Everything a fulfillment operation runs on.

Each client gets a login to their own slice of your operation. They stop emailing you for stock counts and tracking numbers because it is all in front of them.

• Live inventory for their own stock, with low-stock thresholds they set per product and alert emails when a product drops below them
• A new-order form that only shows their catalog and their saved recipients, with an address book shared across their team
• Order history with status and UPS tracking, CSV export, and self-service edits and change requests
• Restock requests when they are sending you more stock, reviewed and approved on your side
• Invoices, credit balance and payment history, with downloadable reports: invoice report, order history, inventory snapshot, credit statement, account summary
• Team members with per-person permissions, and sign-in protected by an emailed verification code
• Lots and certificates for their products, with a public certificate page per lot (see inventory below)

Stock is tracked per client and per SKU, with an append-only quantity ledger behind every number. Lots are created at receiving and follow the product to the order line, the packing slip and the shipping email.

• Per-client stock: a client's orders only ever draw from that client's own inventory; stock you hold for yourself is kept separately
• An inventory health view that flags negative quantities, over-committed SKUs and any count that has drifted from its ledger, with a reconciliation tool to fix it
• Lots from receiving with the client's own lot number, received date, best-by and expiry, remaining units and which orders they shipped on
• Certificates of analysis attached to a lot, or testing requested from a lab you've set up; anyone who scans the lot's code reaches its public certificate page
• Low-stock alerts per product, and a watch list for products a client wants to keep an eye on
• Product pictures and barcodes per SKU so the floor picks by sight and by scan
• Switchable per client: general-merchandise and perishables clients skip lots, kits and certificates entirely

When an order asks for more than is on hand, Lithos raises a shortfall and holds the order instead of shorting it quietly. Your staff decide how to resolve it, and the client sees the result.

• Automatic shortfalls on portal and API orders, with the order held in a review state until resolved
• Fill from existing inventory when the client's own stock can cover it
• Ship less, backorder the rest: choose the quantity per short item; the remainder becomes a child backorder that stays owed
• Substitutions offered by staff and accepted or declined by the client in the portal or through the API
• General restock requests from clients flow into an editable invoice; paying it opens a pending receipt for the incoming stock
• Order holds for bad addresses at intake: held for a fix, never rejected

Inbound stock is a receipt with lines to fulfil. Fulfilling a line adds the units, creates the lot, and hands the floor a shelving task with checkpoints, so nothing is received into a spreadsheet and lost on a cart.

• Pending receipts per client with ordered, fulfilled and still-pending quantities per SKU, visible to admin and warehouse
• Lots on fulfil: each fulfilled line creates a lot with the client's lot number and dates, and emails the client that stock was released
• Shelving tasks ("Shelve 120 × SKU for client, lot …") assigned to a staff member with pull, place and count checkpoints, in a "My work" list with an email on assignment
• Suspended inventory: stock received but held out of on-hand at the client's request, released later by quantity and lot
• Inbound shipment notices through the API for clients who send their own SKUs, so receipts are waiting before the truck arrives
• Purchase orders and suppliers for stock you buy yourself, with receiving against the PO
• Create-from-scan for new barcodes at the receiving bench

A client can fix their own pending order right up until a shipping label exists. After that, edits become change requests your staff handle, so the floor is never packing against a stale order.

• Self-edit until a label is bought: quantities and ship-to on a pending order, from the client's own order list
• Change requests after a label exists, or for anything the client can't edit themselves, shown as a count on the operator's orders screen and handled in place
• Cancel and request a return from the same row; cancelling restores the client's stock through the ledger
• Edits are locked by the label on the staff side too: void the label, edit, re-label
• Order notes from the client and internal notes for staff, kept apart
• Combine orders going to the same recipient before they ship
• Replacement orders for reships at your cost, tracked as such for billing

UPS is connected directly. Rates, labels, voids, reprints and tracking happen inside Lithos, on whichever UPS account should pay for the shipment.

• Rates with real delivery dates, Saturday delivery and signature options, using negotiated rates
• Your master account or the client's own: a client connects their UPS account and ships at their rates; or bill a shipment to a third-party account number
• Labels from the pick list, with void, reprint and return labels
• Tracking written back to the order and polled until delivered; clients see transit updates in the portal, buyers get shipped and delivered emails
• Address checks at intake: impossible addresses are held for a fix rather than rejected, and normalised before the label is bought
• Ship-from branding per client on labels and packing slips, so the buyer sees the client's name, not yours
• Rebilling: labels bought on your account for a client roll into a consolidated shipping invoice for that client (see billing)

UPS is the only carrier today. coming Other carriers are on the roadmap; Founding Operators set the order.

The warehouse works from one queue. Pick, verify by scan, print what the box needs, ship. Lot numbers and the client's branding come along without anyone looking them up.

• A pick list ordered by age, filterable by client and status, printable, with ship and mark-sent actions on each row
• Scan-to-verify picking with a handheld barcode scanner; every scan is recorded, and skipping the scan is recorded too
• Packing slips with lot numbers per line and the client's ship-from branding
• Label printing for products and lots, from a client's own label artwork with the lot, expiry and a QR to the certificate page
• Print queues for shipping labels, packing slips, pick lists and product labels, served to a small print agent on the warehouse PC
• Warehouse dashboard with throughput, orders by client and top shipped products

Bill the work a 3PL actually does: boxes shipped, storage, handling and the labels you bought on a client's behalf. Invoices live where your clients already look, and the ledger behind them is one you can defend.

• Invoices tied to an order or standing alone: storage fees, retainers and ad-hoc charges are ordinary invoices with their own line items
• Shipping rebilled automatically: labels bought on your master UPS account for a client consolidate into a per-client shipping invoice
• Statuses that mean something: unpaid, paid, overdue, pending approval; paid invoices lock
• A credit ledger per client: deposits, invoice payments, adjustments and refunds, with the balance visible to the client
• Pay from credit in the portal when you allow it; invoice emails and PDFs; weekly statements if a client wants them
• No card processor in the way: clients pay you the way they pay you today; Lithos keeps the record
• Replacements at your cost are flagged so they drop out of what you bill

When a client asks what happened to an order, you can answer in a minute, with the record to back it.

• An immutable audit log of admin actions: who, what, which record, when
• Order trace: who placed an order, from which IP and device, exportable as CSV for a date range
• An email log of every message Lithos sent, to whom, with delivery status
• Quantity ledger behind every stock number, so a count can always be explained
• Sessions listed per user, with sign-out of other devices, and emailed sign-in verification codes
• Report an issue from any screen, capturing the page, role and version for your support request

For clients with their own systems, a REST API scoped to one client per key, and signed webhooks for the events that matter.

• Per-client API keys with read or write scope, IP allow-lists and rate limits; a key can only ever see its own client
• Reads: inventory, products with prices, orders with tracking, invoices, lots, documents, packing slips, labels, reports and CSV exports
• Writes: create orders (deduplicated by your order id), cancel, update ship-to while pending, respond to shortfalls and substitutions, manage the address book, request restocks
• Own-SKU clients can create and update products and send inbound shipment notices ahead of the truck
• Webhooks signed with HMAC, with retries, a delivery log and replay: order created, status changed, shipped, label created, needs review, approved; invoice created and paid; inventory low and updated; product image changed
• Bulk import of products by CSV on the operator side, CSV export of orders and reports on the client side
• Store connectors for Shopify, WooCommerce and BigCommerce coming