In this guide10 sections
The essentials
- Keep the shop order, warehouse SKU and approved instruction version connected.
- Check cancellations and changes through the agreed order channel before release.
- A prepared label and a physical carrier handover are different events.
Agree what each stage means
| Order stage | What needs to be clear | Useful record |
|---|---|---|
| Order received | The team has the order reference and the agreed data needed to review it. Receiving information does not by itself approve packing or dispatch. | Order reference, source channel and instruction version. |
| Waiting for clarification | A variant, stock quantity, personalisation or change needs a decision. Agree whether the order can be held and who answers the question. | The open question, decision owner and agreed next update. |
| Approved for preparation | The product mapping, quantities and packing version have been reviewed through the agreed approval process. | The approved instruction and who approved this stage. |
| Handed to the carrier | Confirm the physical handover separately from label creation. Carrier event wording and scan timing vary by network. | The collection or acceptance record, shipment reference and available tracking. |
| Exception under review | An issue needs follow-up. Agree who checks the evidence, decides the next action and updates the seller. | The issue, latest known event and next action owner. |
Connect the names used by your shop and the warehouse
“Sand” in your listing and “beige” in a supplier file may describe different products. Map the exact variant to a stable stock reference, with a photo or specification where useful. Agree what happens when a reference is missing; a similar-looking item should not silently replace the requested variant.
- Shop variant, warehouse SKU and quantity per order
- Set contents and items that must travel together
- Personalisation reference and the approved product specification
Make an instruction version easy to recognise
Use a dated reference for the product, packing layout, insert and label. When you send a revision, name the orders or batch it affects and identify what changed. Ask the team to confirm that the new version replaces the previous one; sending a file alone does not establish that the revision has been accepted or applied.
Give cancellations and changes a clear decision path
Agree who checks the seller’s order channel before preparation and release. ShipStation’s Etsy documentation warns that an Etsy cancellation is not automatically recognised in ShipStation; this is one reason to verify the actual connection rather than assume every status is synchronised. Confirm whether work or collection has already happened before promising a stop or amendment.
- Who checks a cancellation or updated instruction
- Which orders the change affects and whether work has started
- Who confirms a hold, restart or further handling, including any costs
Keep dispatch facts separate from buyer messages
Use the real dispatch location and agreed route. For US-bound Etsy orders, confirm the required DDP arrangement and included charges. Etsy requires sellers to mark an order shipped only after it is actually shipped. Agree who supplies tracking, who updates the shop and who responds to the buyer; this website does not automatically update an Etsy order.
A small example of a useful handover
This is an illustrative mapping for discussion, not a customer case or an approved order. The purpose is to make a mismatch visible before packing.
- Shop variant “Sand / 350 ml” → proposed warehouse reference MUG-SAND-350; confirm the match
- Set quantity: two mugs; proposed packing instruction PACK-v3; approval still required
- Personalisation: use the agreed private order field; [NAME] is only a placeholder in this example
- If the received stock says MUG-WHITE-350, ask for a decision before substituting it
Start with the part that is unclear
Tell us the product and the handover step that is unclear: matching stock, confirming packing, applying a change or checking dispatch. An order reference and a short explanation are enough to start the discussion. Use the preparation guidance below if helpful; buyer addresses and account credentials belong in the agreed secure channel when required.
Put the instructions into practice
The examples below are planning aids based on the service scope. They are not customer cases, shipment approvals or confirmed quotations.
Choose one current order instruction
An order reference should connect the item, variant, quantity, personalisation and packing version. If the seller and warehouse use different SKU names, agree the mapping before relying on either list. Label a revision clearly rather than sending a second instruction that looks like an additional order.
Define what an update is allowed to change
For an address, quantity or personalisation correction, identify the order and the field that changes. Ask the team to confirm whether the change can still be applied at the current stage. Do not assume that editing your store automatically updates goods already being prepared or a parcel already dispatched.
Distinguish received, prepared and dispatched
Agree the meaning of status updates and the references used to match them to an order. A received instruction is different from stock allocation or dispatch confirmation. Identify who reviews duplicates, missing fields and failed updates, and how a manual correction is acknowledged when an automated handover is unavailable.
Before you approve the next step
- Order and stock references have an agreed mapping.
- The latest revision and the intended action are unambiguous.
- Changes, cancellations and duplicate handling have an agreed review path.
Continue with the related task
Ask the team to review your instructionsPlan an order handover
Match the shop variant to its warehouse stock reference and identify the product and packing instruction versions. Clarify quantities, personalisation and any cancellation or change before dispatch. Agree who releases the order and what evidence distinguishes an instruction, a created label and the physical handover of the parcel.
Questions sellers ask
Does sharing order details authorise packing or dispatch?
Sharing information starts the review. The team still needs to confirm the service scope, current instructions, approval process and charges through the agreed arrangement. Make the requested action explicit, particularly when a message changes an earlier instruction.
Can an order always be cancelled after a label is created?
Do not assume so. A label alone does not establish whether work or physical handover has happened. Ask the team to check the current stage and confirm what can still be changed.
What information should I share in the first conversation?
Start with the product, order reference and the task or issue you want to discuss. Use placeholders if an example needs personalisation or delivery fields. The team will confirm which detailed order data is necessary and how to share it through the agreed secure channel; do not include account passwords in an initial message.
Sources behind this guide
Public carrier and industry resources inform these preparation notes. The team confirms the requirements for your product and route.
- ShipStation: Etsy integration requirements
This integration’s order requirements, shipment handover and cancellation limitations explain why connection-specific checks matter.
- Etsy Shipping Policy
Seller responsibilities for actual dispatch location, US-bound DDP, shipment marking and buyer delivery.
- Etsy: third-party shipping providers
Shipping-data permissions vary by application, origin and connection history. A planning checklist does not grant API access.
- FedEx: tracking status meanings
A carrier example distinguishing a prepared label from physical parcel acceptance; other networks use their own events.