Integration
Target Plus integration
mPorts OMS connects to Target Plus. Today this is a read-only connection: mPorts reads inventory and order status, and does not write anything back.
Integration status
Built and tested against the documented contract. Live readiness for your account is confirmed during onboarding rather than assumed.
What data flows
Inventory in
Inventory is read.
Order status in
Order status is read.
Warehouses
Warehouse data is resolved.
What this automates
Work that would otherwise be done by hand in the Target Plus seller interface, one order at a time.
- Inventory read
- Order status read
- Warehouse resolution
What this integration does not do
-
Creating orders
Not supported.
-
Updating inventory
Not supported.
-
Label upload
Not supported.
-
Tracking upload
Not supported.
-
Cancelling orders
Not supported.
-
Which location ships it
Orders pulled from this channel do not say where they should ship from.
Worth knowing
This is the most limited of the connections described here, and it is described that way deliberately. mPorts reads from Target Plus and does not write back to it, so this page claims reads only. If your operation needs writes to Target Plus, that is a scoping conversation, not an assumption.
How authorization is handled
API key, held by the integration layer.
Questions buyers ask
- Which mPorts OMS capabilities use this?
- Orders, Inventory, Fulfillment and Shipping all draw on it. The integration is infrastructure beneath those capabilities rather than a product of its own.
- Is this integration live for our account?
- That is confirmed during onboarding against your own credentials and catalog. We would rather check than assume, because the answer depends on your account's configuration as much as on the integration.