Skip to main content

List ShipMyOrders Inventory Discrepancies

GET 

/api/shipmyorders/inventory/discrepancies

Compares the last ShipMyOrders stock snapshot with SKU.io's available quantity in the warehouse linked to the active ShipMyOrders instance, and returns every linked product where they differ, ordered by SKU.

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Per row: id / sku / product_id (SKU.io product), SKU (the SKU as ShipMyOrders reported it), type (product type), unit_cost, sku_inventory (SKU.io available quantity, 0 when none), smo_inventory (ShipMyOrders stock), discrepancy (smo_inventory - sku_inventory; positive = provider holds more) and discrepancy_value (discrepancy * unit_cost, 2 decimals). component_count is the number of kits the product is a component of.

related (present only when relevant) lists the other discrepant rows a mismatch is probably explained by: for a kit, its components (type: component); for a component, the kits that use it (type: kit). Each entry has id, sku, pivot_quantity (units of the component per kit) and that product's discrepancy.

The top-level warehouse_id is the SKU.io warehouse compared against (null when no active instance exists). No parameters. ShipMyOrders is a deprecated integration: the provider service no longer exists, so nothing is sent to or pulled from it. Historical invoices and inventory snapshots stay readable and manageable.

Authentication: Bearer token (Personal Access Token).

Request​

Responses​

OK

Response Headers
    Content-Type