Ordoro as an IMS Source

July 20, 2026

Summary

Ordoro connects to Flxpoint as an IMS source, running Get Inventory (product data plus quantity), Send Fulfillment Requests, and Get Shipments. It authenticates with Basic Auth today; Ordoro is migrating to API Key credentials (Client ID and Client Secret), and OAuth 2.0 is not supported. Get Source Invoices is not available for this integration.

What this integration does

Get Inventory

Imports Ordoro's product catalog with pricing and stock quantity.

Send Fulfillment Requests

Sends dropship orders (Fulfillment Requests) from Flxpoint to Ordoro.

Get Shipments

Pulls Ordoro shipment confirmations — SKU and quantity shipped.

How to connect - credentials you need

Add an Ordoro source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your credentials, then Test Connection → Save Connection. Ordoro is migrating from Basic Auth (Username/Password) to API Key credentials (Client ID/Client Secret) — use whichever your account currently requires.

Username / Client IDRequired

Your Ordoro username, or — for accounts on the newer API Key auth — the Client ID generated in Ordoro (Account Settings > API Keys > Add API Key).

Password / Client SecretRequired

Your Ordoro password, or — for API Key auth — the Client Secret generated alongside your Client ID. OAuth 2.0 is not supported.

Warehouse IDOptional

The number at the end of the Ordoro warehouse URL. Set it to import only that warehouse's products; leave blank to import all available products.

Ordoro is moving from Basic Auth to API Key credentials — enter your Client ID as Username and Client Secret as Password once generated (Account Settings → API Keys → Add API Key). OAuth 2.0 is not supported. Send Fulfillment Requests also needs an Ordoro sales channel ID — see Important Notes.

Important - read before configuring

Switch to API Key credentials

Ordoro is deprecating user-based Basic Auth this year. Generate an API Key in Ordoro (Account Settings > API Keys > Add API Key), then enter the Client ID in the Username field and the Client Secret in the Password field. OAuth 2.0 is not supported.

Expose the Company field to avoid undeliverable packages

The Company field exists in the Shipping and Billing address mappings but is not exposed by default. Add it to your mapping template; missing company information has caused undeliverable packages.

Warehouse ID filters inventory

Set the Warehouse ID (the number at the end of the warehouse URL) to import only that warehouse's products. Leave it blank to import all available products.

Sales channel ID is required for fulfillment

Send Fulfillment Requests need the Ordoro sales channel ID (from the channel URL). If you have no channel to point at, Flxpoint can create a custom cart, or you can use a channel = manual filter and take that ID.

Operations - fields to know

Get InventorySend Fulfillment RequestsGet Shipments

Field	Maps To — Notes
imageUrl	→ Product / Variant → Images. Ordoro's product image URL maps to both product- and variant-level images.
Warehouse On Hand / Available (per Warehouse ID)	→ Inventory → Quantity. When a Warehouse ID is set, only that warehouse's on-hand and available quantity are imported; leave blank to pull all available products.

Source Field	Maps To (Ordoro) — Notes
Fulfillment Request line → SKU / Quantity	→ Order Item. Required. Sent to Ordoro per line item, along with unit cost to calculate the item total.
Shipping Address	→ Ship To. Required. End-customer shipping address sent to Ordoro.
Billing Address → Company	→ Shipping / Billing Address → Company. Not exposed by default — add the Company field to your mapping template in both Shipping and Billing Address sections to avoid undeliverable packages.
Source Shipping Method	→ Ship Method. The shipping method sent to Ordoro for the order.
Warehouse ID	→ Order → Warehouse. When set, the order is sent against that Ordoro warehouse.
Total Weight	→ Order Item → Weight. Looked up from the matching Source Variant record.

Field	Maps To — Notes
Sku	→ Shipment Item → SKU. Required. Associates the shipped line to your catalog.

Common issues

Product coming in with Available Quantity (empty)

A SKU imports from Ordoro but Available Quantity is blank. Verify the product's warehouse assignment and the Warehouse ID setting, then re-run Get Inventory after confirming the SKU has stock in the targeted warehouse.

Packages undeliverable due to missing Company field

Orders sent to Ordoro omit the company name, causing undeliverable packages. Expose the Company field in the Shipping and Billing Address mappings so complete address information accompanies each order.

FAQs

Why is a product's Available Quantity coming in as (empty) from Ordoro?▸

This is a GIP quantity sync issue for that SKU. Confirm the product's warehouse assignment and that the Warehouse ID setting (if configured) matches; a mismatched or blank warehouse can leave quantity empty even when the product exists in Ordoro.

Can I include the Company name on orders sent to Ordoro?▸

Yes. Ordoro's API exposes a company line, but Flxpoint only sends it if you expose the Company field in the Shipping Address and Billing Address sections of your mapping template.

Back to IMS