Mark Sales Orders Shipped Before Tracking
POST/api/sales-orders/mark-shipped-before-tracking
Starts a background job that marks the selected sales orders as shipped before inventory tracking. For each eligible order, every open product line is credited as externally fulfilled (pre-tracked): no inventory movement is created and no inventory debt is recorded, reservations are released, open unsubmitted fulfillment orders are retired, and the order is closed as fulfilled. A note is added to each order. Ineligible orders are skipped and reported in the job results.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the sales_orders.fulfill permission.
Request body fields:
- ids (array of integers, required unless
apply_to_allis true): Sales order IDs to target. Each ID must exist. - apply_to_all (boolean, optional): When true, target every sales order matching
filtersinstead ofids.falsenever widens the selection. - filters (object, optional, used only with
apply_to_all: true): The same filters as List Sales Orders (flat filter keys such aspre_tracking_open,search, orfilter_groups). Omitted or empty targets every order. - push_to_sales_channel (boolean, optional, default true): For Shopify orders, also mark the order fulfilled in Shopify — the customer is not notified and no tracking is added. A Shopify fulfillment reported back afterwards changes nothing in SKU.io.
- reverse_post_start_channel_fulfillments (boolean, optional, default false): For orders already deducted because a channel fulfillment dated on/after the start date was recorded, void that shipment locally (stock is returned; the channel's fulfillment is kept) and credit the units as pre-tracked.
Eligibility — an order is eligible when:
- the account has an inventory start date set, and the order was placed strictly before it;
- the order is not cancelled and at least one product line still has unshipped quantity;
- nothing on it is already with a shipping provider, a dropship supplier, Amazon MCF, awaiting customer pickup, or mid-shipment. Ineligible reasons: not_found, no_inventory_start_date, ordered_on_or_after_start, cancelled, nothing_open, in_flight_fulfillment, submitted_to_provider, dropship_in_progress, active_mcf_order, awaiting_pickup, locked_period, failed.
Response: tracked_job_log_id — poll the tracked job to follow progress. Job results include orders_closed, units_credited, pushes_queued, shipments_reversed, units_returned, orders_skipped, failed_count, skipped[] and errors[].
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.