Reference · built on requestOperator by FibricInventory & supply

Stock Transfer

Finds surplus at one location and shortfall at another, and proposes a transfer order with quantity, route, and shipping cost.

Request accessPricing ↗

About

Two locations can hold the same item in the wrong proportion: one has months of cover, the other days. Stock Transfer reads on-hand and committed units per item and location, the demand each location has shown over the window, transfer orders already in transit, and carrier rates for the lane between them.

Where one location's cover exceeds your ceiling and another's falls below your floor, it proposes a transfer order with the quantity, the from and to locations, and the shipping cost quoted for that weight. An inventory planner approves. The transfer order is entered only then, and the record shows the cover at both ends.

This is a reference listing. It documents what Fibric would read from Stock Transfer and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • On-hand, committed, and On Order units per item and location from NetSuite, Business Central, or Odoo
  • Units sold per location over the window, from Shopify orders by location_id or from ERP sales orders
  • Transfer orders in Pending Fulfillment or Pending Receipt in NetSuite, and shipped but unreceived transfer orders in Business Central
  • Business Central transfer routes with In-Transit Code, Shipping Agent Code, and Shipping Agent Service per lane
  • Carrier rates for the lane through ShipEngine POST /v1/rates or EasyPost Shipment rates, priced for the transfer's weight
  • Item weight and dimensions, so a proposal carries a real shipping quote

Proposed actions

  • Target capability: propose a NetSuite transfer order with From Location, To Location, items, quantities, and Shipping Cost
  • Target capability: propose a Business Central transfer order with Transfer-from Code, Transfer-to Code, and the route's shipping agent service
  • Target capability: propose an Odoo replenishment from a resupply warehouse, which creates the delivery order and the receipt
  • Target capability: propose adding units to a transfer already planned for the same lane, instead of a second shipment

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Rebalance two warehouses after a regional spike

    Shopify orders by location show one warehouse draining while the other stays flat. A NetSuite transfer order is proposed with the quantity and a ShipEngine rate for the weight.

    With Shopify, NetSuite, ShipEngine

  • Fill a store from the distribution center

    Business Central cover at a store falls below the floor. A transfer order on the existing route, with the route's Shipping Agent Service and an EasyPost rate for the cartons, is proposed for the planner.

    With Microsoft Dynamics 365 Business Central, EasyPost

  • Resupply an Odoo warehouse before it runs dry

    Odoo stock at a retail warehouse drops toward the floor. A replenishment from the central warehouse is proposed, with a ShipEngine quote attached, creating the delivery order and receipt when approved.

    With Odoo, ShipEngine

Requirements

  • Multi-location inventory in the ERP: NetSuite with Multi-Location Inventory enabled, Business Central locations with transfer routes, or Odoo warehouses set to Resupply From each other
  • Demand per location for the window, from a storefront or ERP orders
  • A carrier rating account, so the shipping cost on a proposal is a quote rather than an estimate
  • An inventory planner named to approve each transfer order
Authentication
ERP credentials with transfer order entry permission (a NetSuite REST integration with Multi-Location Inventory, a Business Central OAuth app, or an Odoo API user) and a ShipEngine or EasyPost API key for rates.

Limits

  • NetSuite transfer orders exist only with Multi-Location Inventory enabled. Without it, no proposal can be entered.
  • The quantity brings the destination up to your floor without taking the source below its ceiling. It does not chase a forecast.
  • Shipping cost is the rate quoted at proposal time for the stated weight. The carrier's invoice may differ.
  • A proposal covers one lane. Rebalancing three locations is three proposals.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Stock Transfer ↗

Questions and answers

How does it pick the quantity?
Cover at each location is on-hand less committed, divided by that location's daily demand. The quantity moved lifts the destination to your floor without pushing the source below its ceiling, rounded to the item's pack size where one exists.
What does the planner see?
Both locations' cover before and after, the units, the weight, the carrier and service with its quoted cost, transfers already in transit on that lane, and the expected receipt date. The planner can change the quantity or the service, or decline.
What happens after approval?
The transfer order is entered in your ERP in its default status, Pending Approval or Pending Fulfillment in NetSuite. Fulfillment and receipt stay with your warehouse. The record kept here holds the order number, quantities, cost, approver, and time.
Ask about Stock Transfer

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy