Which Skubana orders does Endless import, and what happens when they do not match my products?

Endless imports Skubana orders that are in Awaiting 3PL Export status at the Skubana warehouse mapped to the integration. It checks every hour, and “Import Orders” on the integration imports right away. Connect the Skubana warehouse to one building; Endless imports from the warehouse on the integration’s first building connection. It skips orders it has already imported, including archived ones.

Each order arrives as Ordered, without a sales channel. Endless copies the ship-to address, buyer notes, gift message, and tax, and maps the requested shipping service through carrier mappings. Skubana’s custom fields 1 to 3, its sales channel name, and its labels become order tags. An order with a missing country or postal code arrives as Pending with an alert.

Skubana orders are routed by your routing strategies and allocated through manual processing or automations, like other orders.

When a line’s SKU does not match an Endless product, or the product’s “Requires Shipping” is No, Endless still adds the line with Skubana’s SKU. The order activity shows “Order received from Skubana has … non-existing product” with each SKU and quantity. To fulfill such a line, create the product with the exact SKU, or set the product’s “Requires Shipping” to Yes, then correct the order line.

An order arrives with no line items when Skubana returns it without any items. Endless creates it as Pending and logs “received from Skubana has no line items.” Check the order in Skubana, then add the items in Endless or cancel the order.

“Order Acknowledgement” is off by default. When it is on, after each import Endless tells Skubana to send the imported orders to fulfillment at the mapped warehouse, which moves them out of Awaiting 3PL Export. Endless tries up to three times. When it is off, the orders stay in that status in Skubana, and Endless skips them on later imports.