A promise to export your data sounds reassuring until the file arrives with one quantity beside each SKU. Does that number include committed orders? Damaged goods? Stock still arriving? A buyer should settle those questions while negotiating the relationship, when the handover can still be made a defined deliverable.
Specify what the receiving team must decide
Start with three decisions: what stock can be promised, what work remains unfinished, and which historical references customer service needs. These decisions lead to three deliverables rather than one undifferentiated download.
Shopify illustrates why the distinction matters. Its inventory CSV documentation describes an All states export with separate location rows and inventory-state columns, while the Available export presents available quantities by location. Those are different views of inventory. Neither establishes what a particular warehouse system can export or supplies a complete exit package.
Build a three-file acceptance test
The following is an original desk-designed acceptance framework, not a comparison of provider systems.
| Deliverable | Buyer acceptance question | Unresolved exception |
|---|---|---|
| Inventory snapshot | Can each SKU and location be reconciled by agreed state at a named time? | Unmapped locations or unexplained totals |
| Open-work register | Can every unfinished receipt, order, return and hold be assigned an owner? | Work without a reference or next action |
| Historical reference file | Can service staff connect an order to its shipment and relevant case? | Broken identifiers or missing required records |
Give the incoming operator sample files before the move. Ask it to identify missing fields and demonstrate how the references will be matched. File availability alone is not acceptance; usable identifiers and clear definitions are what make the handover workable.
Keep totals from hiding commitments
Consider an illustrative SKU with 100 units on hand, of which 20 are committed and five unavailable. If these categories are mutually exclusive and exhaustive, 75 are available. A file containing only “100” cannot tell the next operator whether accepting 90 new orders is sensible. This is a simplified arithmetic example, not a claim about how every system defines or calculates availability.
Write the definitions into the handover specification. Include the snapshot timestamp and timezone, treatment of activity after that time, and the person authorized to resolve differences. Where lot, expiry or serial tracking is necessary, request those fields explicitly rather than assuming they accompany an inventory export.
Make delivery and correction contractual tasks
Ask who produces each file, how it is transferred securely, how long correction takes, and what assistance is included in the exit fee. Agree an access period for resolving discrepancies, subject to the applicable agreement and data obligations. Do not retain customer data indefinitely merely because an export is possible.
The commercial test is straightforward: can the provider describe a repeatable handover that your receiving team accepts? A larger export is not automatically better. Three bounded, reconciled deliverables can be more useful than a database dump with no definitions or owner.
Related reading
Sources
- Shopify inventory CSV exports — accessed 2026-10-18.