Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developers.redo.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Extensiv?

Extensiv (formerly 3PL Warehouse Manager / 3PL WMS, sometimes referred to by its host secure-wms.com) is a cloud warehouse management system used by 3PLs and brand-operated warehouses to manage inbound receiving, inventory, and fulfillment. Redo’s Extensiv integration creates a receiver record in Extensiv for every return so your warehouse team can scan and grade returned items against the original order.

​
What Does the Integration Do?

When a return is ready to ship in Redo, the integration creates one receiver in Extensiv per shipment on the return, populated with:
  • Customer and facility identifiers from your Extensiv configuration
  • A reference number in the form {OrderName}-R{returnCountOnOrder} (e.g. #1001-R1) so warehouse staff can tie the receiver back to the original order
  • The external return ID, so Redo can match the Extensiv receiver back to the source return
  • Carrier and tracking number from the return shipment
  • A receiveItems list of SKUs and expected quantities
When Extensiv finishes receiving the items, it fires a ReceiptComplete webhook back to Redo. Redo verifies the signature against Extensiv’s published RSA public key, looks up the matching return by receiver ID, and automatically triggers return processing — refunds, store credit, or exchanges, depending on the return’s resolution. No manual action is required at the Redo dashboard.

​
How to Set It Up

Extensiv setup is handled by Redo support, not self-serve. The Extensiv integration does not yet have a configuration form in the Redo merchant dashboard. To connect Extensiv to your Redo account, contact Redo support with the credentials below and we’ll provision the integration for you.

​
Prerequisites

Before reaching out to Redo support, make sure you have the following from your Extensiv account:
You must have an active Extensiv (3PL Warehouse Manager) account with API access enabled at secure-wms.com.
Extensiv uses OAuth 2.0 client credentials. Your Extensiv admin can provision an API client and provide the Client ID and Client Secret. Redo exchanges these for an access token at https://secure-wms.com/AuthServer/api/Token and refreshes the token automatically before it expires.
The numeric Extensiv Customer ID that represents your brand inside the 3PL’s Extensiv tenant. Ask your 3PL or Extensiv admin for this value.
The numeric Extensiv Facility ID for the warehouse that will receive returns. Merchants with multiple facilities should pick the facility where returns are physically processed.
Your Extensiv admin must enable the ReceiptComplete webhook event and point it at the webhook URL Redo provides during onboarding. Redo’s webhook handler validates each event with Extensiv’s RSA-signed payloads, so no shared secret is required — only the subscription itself.

​
Configuration Steps

1

Send Credentials to Redo Support

Email support@getredo.com with your Extensiv Client ID, Client Secret, Customer ID, and Facility ID. Mention which Redo team the integration is for.
2

Redo Provisions the Integration

Redo support will create the Extensiv integration record on your team and confirm when it’s active. You don’t need to take action in the Redo dashboard.
3

Subscribe the Webhook in Extensiv

Your Extensiv admin subscribes the ReceiptComplete webhook event to the URL Redo provides. This is what enables automatic return processing when items are received.
4

Test the Integration

Create a test return in Redo and generate a shipping label:
  1. Approve the return through your Redo return portal
  2. Confirm a new receiver appears in Extensiv with the expected reference number, carrier, tracking, SKUs, and quantities
  3. Mark the receiver as received in Extensiv
  4. Confirm the return processes automatically in Redo within a few seconds
Returns whose items have no SKU are silently skipped from the Extensiv receiver. Returns where every item lacks a SKU will not create a receiver at all. Confirm your product catalog has SKUs populated before going live.
If a return has multiple shipments (for example, a single return covering items from two original fulfillments), Redo creates one receiver per shipment in Extensiv. The return will store multiple Extensiv receiver IDs and will fully process only when every receiver reports ReceiptComplete.

​
How Long Does It Take?

​
Setup Timeline

StepTimeDescription
Gather Credentials1-2 daysGet OAuth client, Customer ID, and Facility ID from your 3PL/Extensiv admin
Redo Support Provisioning1 business dayRedo creates and validates the integration on your team
Configure Webhook10-15 minutesSubscribe ReceiptComplete in Extensiv
First Return Test10-15 minutesCreate test return and verify the receiver + auto-processing flow
Total Setup2-3 business daysEnd-to-end, dependent on Extensiv admin availability

​
Operational Timing

1

Receiver Creation

Real-time (1-3 seconds) after the return is approved and a shipping label is generated.
2

Return Processing

Automatic via webhook — when Extensiv fires ReceiptComplete, Redo processes the return (refund, store credit, or exchange) within seconds.
3

Warehouse Processing

Varies by warehouse SLA, typically 1-3 business days from the moment the package arrives at the facility.

​
Support

For issues with the Redo integration configuration, return processing, or data synchronization, contact support@getredo.com. For issues with access, API credentials, or warehouse operations, contact your account manager or support team.