Reference · built on requestOperator by FibricInventory & supply

Channel Allocation

Splits stock you cannot list in full everywhere across storefronts and marketplaces, and proposes the quantity to show on each.

Request accessPricing ↗

About

When one pool of stock feeds several channels, the quantity shown on each is a decision, not a fact. Channel Allocation reads available units per SKU from your inventory system or ERP, the units each channel sold over the window, and the margin each channel returns after its fees.

It divides what is available across channels in proportion to demand and margin, holds back the buffer you set, and proposes a listed quantity per SKU per channel. A channel manager approves the split. Approved quantities are written to each channel, and the record kept shows the quantity each one showed before.

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

  • Available units per SKU and location from Cin7 Core, Linnworks Stock/GetStockLevel_Batch, or a NetSuite item record
  • Quantities currently listed: Shopify available per location, Amazon fulfillmentAvailability, and Walmart inventory per ship node
  • Orders per channel over the window, from Shopify orders filtered by channel, Amazon getOrders, eBay getOrders, and Walmart orders
  • Selling price per channel and the fees each marketplace takes, for a margin per unit per channel
  • Inbound units on open purchase orders, so an allocation can note stock due before the next run

Proposed actions

  • Target capability: propose the available quantity per Shopify location through inventorySetQuantities with reason correction
  • Target capability: propose a fulfillment_availability quantity per SKU on Amazon through patchListingsItem
  • Target capability: propose a Walmart quantity per SKU and ship node through PUT /v3/inventory
  • Target capability: propose an eBay quantity change through bulk_update_price_quantity
  • Target capability: propose holding a SKU off one channel by setting its listed quantity to zero for a period

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

What you can build

  • Split a scarce SKU between Shopify and Amazon

    Available units from Cin7 Core, sales by channel from Shopify orders and Amazon getOrders. A listed quantity per channel is proposed; approved figures go to inventorySetQuantities and patchListingsItem.

    With Cin7 Core, Shopify, Amazon SP-API

  • Favor the channel with the better margin

    When Walmart and eBay both sell a SKU held in Linnworks, the proposal shows margin per unit on each. The manager approves a split that leans toward the higher one.

    With Walmart Marketplace, eBay, Linnworks

  • Pull a SKU from marketplaces before a promotion

    Stock reserved for a Shopify promotion is held back by proposing a zero quantity on Amazon and Walmart for the period. A later proposal restores the split.

    With Shopify, Amazon SP-API, Walmart Marketplace

Requirements

  • One inventory system that holds the true available quantity per SKU: Cin7 Core, Linnworks, or NetSuite
  • At least two sales channels with an inventory write endpoint: Shopify, Amazon, Walmart Marketplace, or eBay
  • Fee or margin figures per channel, entered once and updated when a marketplace changes them
  • A channel manager named to approve each allocation
Authentication
Read access to your inventory system, plus per-channel credentials: a Shopify token with write_inventory, an Amazon SP-API authorization with the Product Listing role, a Walmart Marketplace token, and an eBay user token.

Limits

  • Amazon inventory reports are not near real time. Amazon states a stock data freshness SLA of 3 hours, so Amazon reads are aged accordingly.
  • A listed quantity written to a channel is a ceiling, not a reservation. Sales on other channels still draw down the same stock.
  • The split applies to SKUs sold on more than one channel. A SKU on one channel keeps its full available quantity.
  • Marketplace rate limits pace writes. Amazon's default usage plan allows 5 patchListingsItem requests per second.

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 Channel Allocation ↗

Questions and answers

How is the split calculated?
Available units, less the buffer you set, are shared across channels in proportion to each channel's units sold over the window, weighted by margin per unit. Whole units only. The proposal shows the share each channel gets and the two inputs behind it.
What does the channel manager approve?
A table per SKU: available units, current listed quantity per channel, proposed listed quantity per channel, and the sales and margin used. The manager can edit any cell or decline the SKU. Nothing is written until approval.
Does it ever change a listed quantity on its own?
No. Every quantity written to Shopify, Amazon, Walmart, or eBay comes from an approved proposal. The record stores each channel's previous quantity, the approved one, who approved, and when. The previous figures can be reproposed to undo the change.
Ask about Channel Allocation

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