How do you allocate limited inventory across channels?

Last updated: 2026-08-09

Written and reviewed by Seller Profit Guard Editorial Team.

Multi-Channel Inventory Allocation Formula and Inputs flow from physical stock and reserve through channel demand, allocation, contribution, decision, and restoration — Use the allocation formula ledger to allocate one reconciled whole-unit pool.

Name the physical SKU

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 1 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For name the physical sku, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Use invented or approved SKU-level aggregates only. Exclude private emails, buyer identities, addresses, order rows, payment details, bank records, credentials, invoices, contracts, and raw inventory or order exports from the public allocation formula ledger.

Reconcile available units

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 2 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For reconcile available units, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Exclude unavailable stock

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 3 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For exclude unavailable stock, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Protect reserve units

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 4 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For protect reserve units, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Align forecast horizon

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 5 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For align forecast horizon, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

allocation formula ledger: align forecast horizon — Original explanatory diagram for align forecast horizon using invented SKU-level aggregates and no private seller data.

Estimate retained demand

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 6 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For estimate retained demand, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Estimate contribution

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 7 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For estimate contribution, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Set service floors

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 8 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For set service floors, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Allocate whole units

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 9 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For allocate whole units, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Close evidence

Reconcile one physical whole-unit SKU pool, exclude unavailable and protected reserve units, and estimate every channel on the same forecast horizon. Give each channel a demand-capped service floor, then allocate remaining units either equally or by contribution per retained unit. Compare projected contribution, unmet demand, evidence, and restoration before any live change. Keep physical stock, exclusions, reserve, demand, economics, service, platform behavior, authorization, and restoration separate. Checkpoint 10 in the allocation formula ledger records physical SKU identity, unit of measure, cutoff, availability exclusions, reserve purpose, forecast horizon, source version, owner, reviewer, accepted formula, authorization boundary, and restoration before interpretation.

For close evidence, keep physical, committed, picked, transferred, damaged, quarantined, inbound, campaign-locked, reserved, and allocatable units separate from demand, contribution, floors, allocation, unmet demand, threshold, conflict, backup, stop rule, and restoration.

Name the physical SKU: verification test 1

Create one synthetic counterexample for name the physical sku. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Reconcile the counterexample against a dated physical count, commitments, picks, transfers, damage and quarantine, inbound status, campaign locks, mature order and return aggregates, contribution packet, service obligation, listing and fulfillment state, official platform definition, source version, owner, reviewer, protected baseline, stop trigger, and restored result.

Explain why the test does not prove demand, prevent overselling, predict returns, detect hidden system commitments, control platform routing or reallocation, guarantee contribution or service, authorize inventory edits, establish accounting treatment, or replace tax, legal, contract, provider, marketplace, and qualified-professional review.

Reconcile available units: verification test 2

Create one synthetic counterexample for reconcile available units. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Exclude unavailable stock: verification test 3

Create one synthetic counterexample for exclude unavailable stock. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Protect reserve units: verification test 4

Create one synthetic counterexample for protect reserve units. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Align forecast horizon: verification test 5

Create one synthetic counterexample for align forecast horizon. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Estimate retained demand: verification test 6

Create one synthetic counterexample for estimate retained demand. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Estimate contribution: verification test 7

Create one synthetic counterexample for estimate contribution. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Set service floors: verification test 8

Create one synthetic counterexample for set service floors. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Allocate whole units: verification test 9

Create one synthetic counterexample for allocate whole units. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Close evidence: verification test 10

Create one synthetic counterexample for close evidence. Change one availability, lock, reserve, demand, contribution, service-floor, listing, fulfillment, threshold, or evidence field; retain the prior packet; and show equal and priority channel units, allocated total, residual stock, unmet demand, projected contribution, and Block, Review, or Ready effect.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 1

Reperform name the physical sku with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Archive the accepted packet before varying the field. Explain allocatable units, each channel allocation, residual units, channel coverage, unmet units and percentage, projected contribution, decision, sensitivity driver, monitoring trigger, authorized-owner boundary, stop condition, and restoration path.

The exercise remains educational and source-linked. It does not change inventory, activate listings, alter routing, enter a campaign, bind shared stock, move physical units, guarantee sales, access private records, or replace operational, provider, carrier, marketplace, employment, legal, tax, accounting, insurance, contract, or qualified-professional review.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 2

Reperform reconcile available units with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 3

Reperform exclude unavailable stock with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 4

Reperform protect reserve units with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 5

Reperform align forecast horizon with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 6

Reperform estimate retained demand with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 7

Reperform estimate contribution with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 8

Reperform set service floors with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 9

Reperform allocate whole units with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Multi-Channel Inventory Allocation Formula and Inputs: evidence exercise 10

Reperform close evidence with invented equal and contribution-priority packets. Hold SKU identity, physical count, exclusions, reserve, forecast dates, channel demand, contribution definitions, service floors, listing and fulfillment eligibility, and whole-unit rules constant where a clean strategy comparison requires them.

Sources and further reading

Shopify Help: Order routing: Official location-priority, inventory, split-fulfillment, market, proximity, cost, capacity, and routing context.
Shopify Help: Inventory across locations and apps: Official separate-location inventory, availability, capacity, regional demand, reserved-store inventory, and fulfillment-app context.
Shopify Help: Fulfillable inventory: Official sellable availability, shipping-zone, routing, stockout, and oversell context.
TikTok Shop: FBT shared inventory: Official shared-pool, even distribution, sales-based reallocation, campaign-lock, stockout, binding, and manual-control limitations.
Seller Profit Guard methodology: Evidence, privacy, calculation, review, correction, release, and restoration controls.

Related Seller Profit Guard tools

Multi-Channel Inventory Allocation Calculator: Compare equal and contribution-priority allocation.
Reorder Point Calculator: Plan replenishment triggers separately.
Safety Stock Calculator: Model future uncertainty stock separately.
Stockout Cost Calculator: Estimate stockout consequences.
Methodology: Review evidence, privacy, calculation, correction, release, and restoration.
Data Privacy: Protect seller, buyer, order, payment, inventory, and raw-export data.
Equal Inventory Allocation Worked Example: Reperform an invented equal-after-service-floor allocation with whole-unit rounding, demand caps, reserve, unmet demand, and contribution.
Contribution-Weighted Inventory Allocation Example: Model a materially different priority allocation that preserves floors and assigns residual stock by contribution until demand is filled.
Multi-Channel Inventory Allocation Mistakes: Diagnose duplicate stock, unavailable units, horizon, demand, contribution, floor, rounding, routing, campaign, and interpretation errors.
Reliable Multi-Channel Inventory Allocation Data: Map physical stock, locks, reserve, demand, contribution, floors, listing state, campaign state, ownership, review, and restoration to first-party evidence.
Safe Inventory Allocation Decision Thresholds: Separate structural Block, contribution Review, unmet-demand Review, narrow Ready, overrides, monitoring, stop rules, and restoration.
Equal vs Contribution-Priority Inventory Allocation: Hold one stock pool and forecast constant, compare channel unit distributions, and identify which economic or service assumption changes the choice.
Weekly Multi-Channel Inventory Allocation Routine: Turn allocation into a repeatable count, lock, forecast, contribution, floor, authorization, monitoring, exception, and restoration cadence.
Interpret Inventory Allocation Without False Precision: Read unit allocations, projected contribution, unmet demand, coverage, uncertainty, and next action without turning a forecast into authorization.
Inventory Allocation Audit Checklist and Change Log: Preserve physical stock, exclusions, reserve, demand, contribution, floors, strategies, listings, campaigns, sources, review, stop, and restoration.

Next step: Open Seller Profit Guard.

This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.