Understand what a sandbox proves
Shippo documents a test mode for rehearsing label creation without purchasing usable labels. It warns that displayed test rates can differ from live rates and that a test label on an imported order does not mark the order fulfilled. This official example illustrates an evaluation limit: a successful sandbox exercise is not evidence of a live shipping price or completed store integration.
The checklist below is an independent buying framework. AMZ12 has not bought labels or compared carrier performance. Use it to organize your own authorized trial with the provider and fulfillment team.
Build a representative parcel set
Choose a normal domestic order, a heavier parcel, a multi-item order and a destination that commonly causes an exception. Add an international scenario only if the store actually intends to support it. Use measured packaging information rather than estimates copied from a product description.
For each scenario, record the items, packing method, parcel count and required service outcome. Include the packing colleague in this step. A software demonstration based on a conveniently small parcel can miss the decisions that create work on the warehouse floor.
Follow the data from store to label
Check which order fields arrive and how the shipping workspace represents quantity, address and fulfillment status. Identify who can correct an address and where that correction should be recorded. Review the effect on the store’s customer-facing order history.
Ask the evaluator to show how a split order or missing weight is handled. Keep a note of manual re-entry. A process that works for one order through extensive copying may become difficult to supervise when several colleagues work simultaneously. The aim is understandable data flow, not a one-off successful print.
Rehearse recovery, not only printing
Try a canceled packing decision, a duplicate print request and a printer interruption in the permitted test setup. Write the desired recovery before operating the controls. Determine how staff can identify which label belongs to the parcel in front of them.
Ask about label cancellation, unused-label handling and error escalation under the current provider and carrier terms. Record unanswered questions for confirmation. Do not treat a button being present as proof that every carrier or service follows the same rules. Keep a clear distinction between a training label and one valid for dispatch.
Validate the production handoff carefully
Agree on a separate controlled live acceptance step if the business proceeds. It should cover the actual carrier account, intended service, tracking link and update back to the store. Assign someone to approve any real label purchase and to handle a corrective action if the trial fails.
Collect actual service and account terms directly from the provider for your parcel set. Compare like with like, including the operational steps and integrations required. Test-mode numbers and a general marketing example are inadequate evidence for the cost of your real shipment.
Select for daily ownership
Identify who maintains package presets, carrier access, printer setup and shipping rules. Check whether another trained colleague can resolve an ordinary exception using the runbook. A system that depends on one person’s memory introduces an avoidable operating bottleneck.
Choose the option that can demonstrate the required order journey and make its exceptions visible. Preserve the scenario sheet and acceptance notes for onboarding. They become a practical regression checklist when the store adds a carrier, changes packaging or connects another sales channel.
Official reference: Shippo Support: account sandbox test mode. Source checked on 29 October 2026. AMZ12 analysis and suggested checks are independent editorial guidance.