Skip to main content

NuORDER

📄️Update NuORDER SKU Order

Re-reads the order from NuORDER and reconciles its SKU.io sales order: a cancelled NuORDER order cancels the sales order (shipped units stay); added sizes are added; changed quantities follow NuORDER down to what is already shipped or committed to a fulfillment (a NuORDER quantity below that is kept at the shipped amount and recorded in `reconciliation_conflicts`, and the message says so); NuORDER cancelled quantities (its cancelled shipments) are cancelled on the matching lines; removed sizes are deleted or have their open quantity cancelled; shipments recorded in NuORDER are recorded on the sales order.

📄️Send NuORDER Fulfillments

Sends fulfillments NuORDER does not have yet as NuORDER shipments. Pass ids to send specific fulfillments; omit ids to send every pending fulfillment of the portal (up to 500 per request) — the List Pending NuORDER Fulfillments set, so a failed or unconfirmed send is not re-sent (use Retry Failed NuORDER Send). With nothing pending, the call returns 422 'Nothing is waiting to be sent to NuORDER. Retry failed shipments from the Failed tab.' Fulfillments NuORDER already has are skipped, so repeating the call never duplicates a shipment. Work runs in the background, one job per NuORDER order.

📄️Create SKU.io Product from NuORDER Product

Creates a SKU.io product from the size and maps it (or links an existing product with the same SKU). SKU, name and barcode come from the field mappings (Get NuORDER Field Mappings) — by default SKU `{style}-{color}-{size}` (spaces inside a part become hyphens: `ST1-Navy-Blue-10`), name `Product — Colour / Size`, barcode = UPC, Wholesale Price on the wholesale pricing tier and Retail Price on the Retail (or default) tier. Creating the product creates the `Wholesale` tier first when the mappings use it and it does not exist yet.

📄️Get NuORDER Field Mappings

The NuORDER → SKU.io field mappings used when SKU.io products are created from NuORDER sizes (Create SKU.io Product from NuORDER Product and the bulk `create_products` action). `default_mappings` are the built-in rules (derived SKU → SKU, title → product name, UPC → barcode, Wholesale Price → the wholesale pricing tier, Retail Price → the `Retail` tier or, without one, the default tier; when both resolve to the same tier only the wholesale row is kept), `custom_mappings` are the ones saved for this instance, and `effective_mappings` is the result (a custom mapping replaces the default for the same SKU.io field). `available_listing_fields` lists the NuORDER fields a mapping can read and `available_sku_fields` the SKU.io fields it can write (including every pricing tier and product attribute).

📄️Bulk Update NuORDER Products

Runs `map` (link by UPC / SKU only), `create_products` (link, then create SKU.io products for the rest), `unmap`, `archive`, `unarchive`, `delete` or `revenue` (map to a revenue line) over selected size IDs or every size matching the product filters. Up to 50 selected sizes are unmapped, archived, unarchived, deleted or revenue-mapped immediately; everything else runs in the background and returns its tracked job ID. Selected IDs that belong to another integration are ignored.

📄️List NuORDER Inventory

One row per NuORDER size × NuORDER warehouse: the SKU.io available quantity across the SKU.io warehouses mapped to that NuORDER warehouse, the quantity SKU.io sends (`push_quantity`: never negative, 0 below the minimum stock threshold), what was last pushed, future-dated buckets from open purchase orders, overdue incoming units, and a status: `synced`, `variance` (will be pushed), `not_managed` (SKU.io is not the master of stock, or the product is archived/cancelled/removed in NuORDER) or `unmapped` (size or NuORDER warehouse not mapped).