The Extensiv Order Manager Ruby Has Integration is similar to other 3PL native integrations in functionality (Inventory, Orders, Shipments) but Ruby Has also also built into Extensiv Order Manager’s PO functionality. The Ruby Has WMS is called Deposco and will be referenced throughout this document

For assistance with Extensiv Order Manager related requests with the Ruby Has integration, please reach out to your Extensiv Order Manager implementation manager for additional assistance or support@skubana.com if you are no longer in the Extensiv Order Manager onboarding process.

For Ruby Has support please reach out to support@rubyhas.com


Extensiv Order Manager <> Ruby Has Integration Touchpoints

Purchase Orders

  • Ruby Has pulls Purchase Orders from Extensiv Order Manager that are in a “Pending Delivery” status. The Purchase Order will then be created in Deposco.

    • The Purchase Order sync from Extensiv Order Manager to Ruby Has is scheduled to run every 10 minutes by default. The Ruby Has team can configure this to be a different time frame

  • When the Purchase Order is received at Ruby Has (in Deposco), Ruby Has marks the PO line as received in Extensiv Order Manager. This moves the Purchase Order to “Fulfilled” or “Partially Fulfilled” status in Extensiv Order Manager depending on whether all PO lines are received or not.

    • When the PO line is received in Extensiv Order Manager, then the inventory counts that show up in “In Transit” are removed since they have been received into the destination warehouse and are no longer in transit.

Inventory

  • Ruby Has pushes inventory counts to Extensiv Order Manager

    • The inventory sync from Ruby Has to Extensiv Order Manager is scheduled to run every 2 hours by default. The Ruby Has team can configure this to be a different time frame

    Important Note: Ruby Has pushes inventory counts to Extensiv Order Manager only when inventory is put away into pick locations in the Ruby Has warehouse. Note that because of this, there could be potential inventory counts that are not displayed in “In Transit” or in “On Hand” in the Extensiv Order Manager inventory module. The inventory counts potentially missing stems from the amount of time it takes Ruby Has to put away the received inventory into a pick location.

    If this is an issue, the Extensiv Order Manager team recommends communicating with the Ruby Has team to disable the receiving PO functionality. The POs can be received against manually in Extensiv Order Manager when Ruby Has puts away the inventory and communicates those inventory levels to Extensiv Order Manager. This way the inventory counts would stay “in-transit” in the Extensiv Order Manager inventory module until the PO is manually received in Extensiv Order Manager.

Orders

  • Ruby Has pulls Orders from Extensiv Order Manager that are in “Awaiting 3PL Export” status. These sales orders are then created in Deposco for Ruby Has to fulfill.

    • The Order sync from Extensiv Order Manager to Ruby Has is scheduled to run every 10 minutes by default. The Ruby Has team can configure this to be a different time frame

Shipments

  • Ruby Has pushes shipment tracking information to Extensiv Order Manager once orders have been shipped. Extensiv Order Manager will then push the shipment tracking information to the respective sales channel.

  • Ruby Has will push the shipping cost to Extensiv Order Manager in the Carrier Fee column of the orders module


Integration Setup

  1. Download Ruby Has Application in Extensiv Order Manager

    1. The Ruby Has application needs to be installed in the Extensiv Order Manager account. The application can be found here

  2. Ruby Has enable integration

    1. Email support@rubyhas.com and ask for Ruby Has to enable the integration. Note that at this point the integration will be live. Inventory will sync from Ruby Has to Extensiv Order Manager. Any orders in “Awaiting 3PL Export” that are assigned to the Ruby Has warehouse would be sent to Ruby Has for fulfillment and could be processed for fulfillment by Ruby Has. This should only be done after the following Extensiv Order Manager data entry/configuration steps are completed:

      1. Ruby Has 3PL warehouse created

      2. Master Products added in Extensiv Order Manager

      3. Stock is configured for products in Extensiv Order Manager for the Ruby Has warehouse

      4. Shipment Mappings are configured in Extensiv Order Manager

  3. Integration Testing

    1. The following data flows should be tested to confirm the integration is working as expected

      1. Purchase Orders syncing from Extensiv Order Manager to Ruby Has

      2. Purchase Order receipts syncing from Ruby Has to Extensiv Order Manager

      3. Inventory syncing from Ruby Has to Extensiv Order Manager

      4. Orders syncing from Extensiv Order Manager to Ruby Has

      5. Shipments (tracking information) syncing from Ruby Has to Extensiv Order Manager

Did this answer your question?