Reference · built on requestOperator by FibricOrders & fulfillment

Restock Routing

Reads inspected returns against stock by location and open orders, then proposes where each unit goes: shelf, outlet, vendor, or bin.

Request accessPricing ↗

About

A returned unit that has been graded still needs a destination, and the right one depends on where demand is. Restock Routing reads the received line and its condition from the warehouse, stock for the same SKU at every location, the open orders and backorders waiting on it, and whether the supplier takes that item back.

For each unit it proposes one route: restock at the receiving location, transfer to the location with demand, list on the outlet channel at the recorded grade, raise a vendor return, or dispose. A person approves each route, and the return record keeps where the unit went and why.

This is a reference listing. It documents what Fibric would read from Restock Routing 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

  • Received return lines in ShipHero with quantity_received, condition, and the warehouse that took them in
  • NetSuite return authorizations in status Partially Received or Pending Refund, with the item receipt behind each line
  • On-hand and available quantity per location from Shopify inventory levels, Katana inventory, or Cin7 Core
  • Open orders and backorders waiting on the same SKU, grouped by fulfilling location
  • Vendor terms per item: whether the supplier accepts returns and the vendor RMA number a return authorization needs
  • The outlet or B-stock channels you sell through and the condition grades each one accepts

Proposed actions

  • Target capability: propose a restock at a named location through inventoryAdjustQuantities with reason restock_return, or the equivalent receipt in your inventory system
  • Target capability: propose a transfer to the location with open orders on the SKU instead of the location that received the unit
  • Target capability: propose a NetSuite Vendor Return Authorization for units the supplier accepts back, with the vendor RMA number on it
  • Target capability: propose listing a unit on the outlet channel at its recorded grade, or a disposal adjustment with reason damaged
  • Target capability: propose a note on the return record naming the route each unit took

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

What you can build

  • Send the unit where the order is waiting

    A return received in ShipHero at one warehouse while a backorder waits at another gets a transfer proposal, not a restock in place.

    With ShipHero, Shopify

  • Return defective units to the supplier in batches

    Units graded defective for a vendor that accepts returns are grouped into one proposed Vendor Return Authorization in NetSuite, with the RMA number and the Cin7 Core receipt references.

    With NetSuite, Cin7 Core

  • Keep opened goods off the main shelf

    An opened but working unit received in Logiwa is proposed for the outlet channel at grade B; the Shopify adjustment lands in the outlet location, not sellable stock.

    With Logiwa, Shopify

Requirements

  • A warehouse or returns system that records received quantity and condition per unit: ShipHero, Logiwa, or Cin7 Core
  • Inventory by location from your store or inventory system, so a unit can be routed toward demand
  • A routing table you maintain: condition grade to destination (sellable, outlet, vendor, disposal) by product family
  • NetSuite with the Vendor Return Authorizations feature enabled, if vendor returns are one of the destinations
  • A named approver for vendor returns and disposals
Authentication
Warehouse, store, and ERP connectors each hold their own credential: a ShipHero API token, a Shopify app token with write_inventory, and a NetSuite integration with the Credit Returns permission.

Limits

  • Condition is whatever the receiving system recorded; a unit with no grade gets no route and is listed for inspection
  • A vendor return needs the supplier's RMA number; without one the proposal stays open until a person adds it
  • A transfer is a change to your inventory records; the physical move is scheduled by your warehouse
  • It does not price outlet units; it proposes the channel and the grade

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 Restock Routing ↗

Questions and answers

What is the approver asked to confirm?
A route per unit: restock at a named location, transfer to another, vendor return, outlet, or disposal. The proposal shows the recorded condition, stock at each location, open orders on the SKU, and the routing rule it applied.
What trail does each unit leave?
An inventory adjustment or transfer with a referenceDocumentUri back to the return, a vendor return authorization number where one was raised, and a note on the return naming the route, the approver, and how to reverse the move.
Can it move stock or raise a vendor return by itself?
No. Adjusting stock, raising a vendor return, listing on an outlet, and writing off a unit are all proposals until someone approves them, and an approved route is applied once. Ungraded units and units matched to no return wait for a person.
Ask about Restock Routing

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