How to configure Extensiv Warehouse Management (Scout) in techSHIP [Guide]
Last updated: November 2, 2026
Extensiv Warehouse Management, also known as Scout, connects to techSHIP to import outbound orders and send shipment results back to their documents and cartons. This integration is separate from Extensiv 3PL Warehouse Manager.
Onboarding Requirements
Collect the following information before configuring the connection.
DATA ELEMENT | SOURCE AND PURPOSE |
|---|---|
Api key and Api secret | Obtain the API credentials for the intended Extensiv Warehouse Management environment from your account administrator. |
Client account number | Obtain the source client's account number from Extensiv. Use it to match the client in techSHIP and to synchronize its items. |
Outbound document identifier | Obtain the document ID or document number of an outbound order to import. |
API request allowance | Confirm the allowance associated with your Extensiv account before changing the hourly request limit. |
Ensure the Extensiv Warehouse Management integration is enabled for the applicable techSHIP location.
Connection Configuration
Open Settings → My Location for the connected location.
WMS Tab
Configure the following fields:
FIELD | PURPOSE |
|---|---|
Api key | Enter the API key for the selected environment. |
Api secret | Enter the corresponding API secret. |
Test mode | Enable to connect to the test environment at |
Hourly API request limit | Enter a positive request limit appropriate for the account. The default is |
Enable WMS Trace | Enable integration tracing when investigating import or shipment-update problems. |
The connection uses Basic authentication with the supplied credentials. Use credentials authorized for the selected environment.
The integration shares its request allowance across operations using the same API key and environment. It also limits requests to 100 per minute. Operations may wait when the allowance is exhausted.
Click Save to apply the settings.
Client Configuration
Match the techSHIP client's code to the source client account number in Extensiv. Order import identifies the client from the document's shipping-origin client account number.
If the source document does not contain that account number, the integration returns DEFAULT for client routing. Correct the source data or confirm the intended routing before processing orders.
Integrations Tab
Open the applicable Client Account's Integrations tab.
FIELD | PURPOSE |
|---|---|
Update Orders | Enables shipment-result updates to Extensiv, including carton tracking numbers and the document ship date. |
Do Not Update Carrier | Preserves the carrier and service in Extensiv during shipment updates. Leave unchecked when these values should be updated from techSHIP. |
Update Freight | Enables carton shipping-charge updates and the document shipping amount, including applicable markup. This option is displayed when Update Orders is enabled. |
Click Save to apply the Client Account settings.
Order closing is not supported. Sending shipment results does not close the source document. Complete any required closing process in Extensiv.
Importing Orders
Import one outbound document at a time using either:
Trans. ID: Enter the Extensiv document ID.
Order #: Enter the Extensiv document number.
Use one identifier for the intended document. If an Order # matches multiple documents, import using Trans. ID instead. Receiving documents cannot be imported as outbound orders.
The integration imports the available ship-to and ship-from details, order references, items, quantities, and applicable lot and serial numbers. The source shipping-paid amount becomes the commercial-invoice shipping charge.
Carrier and service are taken from the first carton containing routing information. An empty carrier can be used with the client's configured Rate Shopping workflow.
Cartons and Package Data
Existing Extensiv cartons are imported as packages with their items. When the document has no cartons, its item lines are imported into one package.
Packed weight and dimensions: These are not supplied by the integration. Complete and verify the package measurements required by the selected carrier before processing.
Item prices and units: Carton lines receive prices and units of measure from matching document lines. These values can remain empty when the match is ambiguous; review them before processing shipments that require them.
Carton mode: Use Default to retain source cartons or Merge to combine their contents into one package. Cartonization requires the applicable techSHIP item and box configuration.
Shipment readiness: The integration does not select orders by a ready-to-ship status or recheck source-order eligibility before shipping. Confirm that the source document is ready.
Configured order, line, and package flex mappings can override imported values. Review those mappings when imported data differs from the source document.
Sending Shipment Results
With Update Orders enabled, each package being updated must have a tracking number. The integration sends carton tracking, carrier and service unless excluded, and the document ship date during a whole-order update.
Repacking and Carton Replacement
Repacking in techSHIP changes the cartons in Extensiv when the whole order is updated. This includes merging packages, cartonization, and package-content changes.
The integration reuses a matching carton when its contents still match the package. When replacement is necessary, it removes unused source cartons and creates cartons for the current packages.
Review the package contents before sending the update. New cartons require item SKUs and positive quantities.
A single-carton update does not remove other cartons. If a repacked order requires carton replacement, update the whole order.
Shipping Charges
With Update Freight enabled:
Each carton receives its package shipping charge plus its share of the markup.
When package charges are unavailable, the order shipping amount plus markup is distributed across the packages.
The final package receives any rounding remainder.
A whole-order update also sends the document shipping-paid amount and available shipping tax.
The integration does not send shipping labels, BOL documents, POD documents, or PRO numbers to Extensiv.
Voiding a shipment in techSHIP does not cancel the source document in Extensiv. Handle source-document cancellation separately.
Item Synchronization
Item synchronization retrieves the parts associated with the Extensiv client account number that matches the techSHIP client's code.
It imports the SKU, available description, and positive shipping weight. It does not supply item dimensions or harmonized codes.
Confirm item weights before using them for shipping calculations: the integration treats the supplied shipping weight as pounds.
Troubleshooting
Authentication or connection failure: Check Api key, Api secret, and Test mode in the location's WMS tab. Confirm that the credentials are valid for the selected environment.
Order cannot be found or is ambiguous: Check the outbound document identifier. If Order # matches more than one document, use its Trans. ID.
Receiving document rejected: Select an outbound document. Receiving documents cannot be processed as outbound shipments.
Missing weights, dimensions, or customs values: Complete the required package measurements and review item prices, units, and customs information before requesting carrier rates or labels.
Shipment results are not updated: Check Update Orders on the Client Account's Integrations tab and confirm that every package being updated has a tracking number.
Carrier or service remains unchanged: Check Do Not Update Carrier on the Client Account's Integrations tab.
Shipping charges are missing: Check Update Freight and the order's shipping charges and markup. Document totals are sent during whole-order updates.
Repacked order cannot update one carton: Update the whole order so that Extensiv cartons can be reconciled with the current packages.
Update partially succeeded: Review the error and retry the same shipment update after correcting its cause. The integration identifies cartons already created for the packages so that retries can reuse them.
API request-limit timeout: Retry the same operation later. Confirm Hourly API request limit and use a consistent value for locations sharing credentials.
Item synchronization fails: Confirm that the client's code matches exactly one Extensiv client account number and that its item SKUs are populated and unique.