An order entering WooCommerce is not always ready for shipping. Norml scopes a Zapier handoff that checks the agreed payment and order conditions, maps the required shipping details and records ShipStation's acceptance. We inspect the existing WooCommerce–ShipStation connection first, so another order feed does not compete with a working import.
The workflow ends with a verified order handoff. Buying a label and physically dispatching a parcel remain separate actions.
Review native ShipStation imports, existing Zaps and manual order entry before adding a route. If the native connection already covers the requirement, the useful work may be fixing its configuration or documenting exceptions.
Agree the payment evidence, included order statuses, shipping methods and products. WooCommerce's order-created event can include unpaid orders; it cannot stand in for a payment check. Subscription renewals and manual payments need explicit decisions.
Map order identity, recipient address, SKU, quantities and shipping service. Record the returned ShipStation identifier and handoff result. Missing addresses, unknown SKUs and rejected requests go to an exception queue before anyone treats the order as accepted.
An address edit or cancellation may arrive after import. Define who checks ShipStation and which changes can still be applied. We do not assume an imported, labelled or shipped order can be safely overwritten.
Label purchases, carrier selection, customs decisions, split shipments, refunds and customer notifications require explicit scope. This automation does not mark a parcel dispatched merely because ShipStation accepted an order.
Review paid, unpaid, cancelled and mixed-product examples. Identify the current importer and choose one route that owns each included order.
Use a stable store-and-order reference, save destination IDs and check prior acceptance before retrying. Confirm what the selected Zapier action does when an order already exists.
Repeat the same event, omit a required address field and interrupt the acknowledgement step. Confirm that the fulfillment owner can distinguish a rejected request from an accepted order whose response was lost.