For fulfillment operations holding client stock

3PL software that keeps other people's stock honest.

Q: Can I move clients to SHIP-OS one at a time?

Yes. Inventory authority is set per client. Each client moves on their own timeline: dry-run reconciliation, a physical opening count, a publish preview, then a clean hard switch — with rollback planned. Clients still on their commerce platform mirror cleanly in the meantime.

Q: How does storage billing work?

Once a client's inventory passes an objective trust gate — opening count complete, reconciliation clean, dead letters at zero, publish preview approved — storage invoices draw from the same counted ledger that publishes availability. Accuracy becomes billable revenue.

Q: Do client storefronts get accurate availability?

Yes. True available-to-sell — on-hand minus commitments, unsellable stock, and safety buffers — publishes back to each client's Shopify, with separate pre-order and backorder feeds so controlled sales never contaminate physical counts.

Q: Can one client's stock fulfill another client's order?

No. Ownership is enforced at every level of the inventory model — receiving, bins, movements, and allocation — so one client's units can never silently cover another client's order.

Q: What do my clients see?

A real customer portal on your own verified domain: their shipments, inbound inventory, billing, and returns, plus private channels and a permanent thread per order — staff join only when invited.

You hold it, you pick it, you bill for it — so the inventory system has to be authoritative, per client, with custody you can prove and availability your clients' storefronts can trust. That's the whole design.

Onboarding, per client

Every client cutover, on its own timeline.

01 Dry run

Mirror the client's platform and reconcile — discrepancies become findings, never silent writes.

02 Opening count

Go-live starts from what's physically on the shelf, counted into bins.

03 Trust gate

Count complete, dead letters at zero, publish preview approved — an objective checklist, not a waiting period.

04 Authority + billing

One clean switch: SHIP-OS becomes the system of record and storage billing draws from the ledger.

What the ledger guarantees

One client's stock can never fulfill another client's order. Ownership enforced at every level — receiving, bins, movements, allocation. No silent borrowing across accounts.

Custody you can prove, down to the serial. Bin-level tracking with lot and serial identity; every move — putaway, transfer, QC, damage — is a linked movement, not a number edit.

Their storefronts sell only what's there. True available-to-sell publishes to each client's Shopify, with separate pre-order feeds. Returns are inspected before restock, so availability is never inflated.

Storage billing from a ledger you can defend. Invoices assemble from the counted, trusted ledger after the trust gate — storage, handling, postage, recurring fees — and reconciliation shows exactly which line drifted if the invoice doesn't match the movements.

Bad integration data quarantines, never applies. Unmapped writes land in an observable dead-letter queue with safe replay; post-cutover drift raises alerts naming the client, SKU, bin, and fix.

Your clients, inside the loop.

Clients log in to the portal on your own verified domain — shipments, inbound inventory, billing, and returns — with private channels and a permanent thread per order. Staff join only when invited.