multi-warehouse

Allocate orders to optimal fulfillment locations across multiple warehouses.

14|3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill multi-warehouse-tomtoto757
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-warehouse
Source: https://github.com/tomtoto757/ecomm-ai-skills-hub/tree/main/skills/catalog-inventory/finsilabs/catalog-inventory/multi-warehouse
Command: npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill multi-warehouse-tomtoto757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merchants and engineering teams struggle to route orders correctly when inventory is distributed across multiple warehouses, stores, or 3PLs, causing higher shipping costs, delayed delivery, and customer confusion from split shipments. This Skill provides clear operational guidance and implementation patterns to allocate orders, manage transfer orders, and surface split-shipment messaging to customers.

Core Features & Use Cases

  • Proximity-first allocation: Score active fulfillment locations by distance and prefer a single-location fulfillment when possible to minimize splits and shipping costs.
  • Greedy split fallback: When no single location can fulfill an order, assign items to the nearest locations with available stock and produce one fulfillment record per location.
  • Transfer order lifecycle: Create, ship (reserve at source), and receive (decrement source on_hand+reserved and upsert destination on_hand) transfer orders with atomic updates and partial receipt support.
  • Platform guidance: Step-by-step setup notes for Shopify, BigCommerce, WooCommerce, and custom/headless implementations plus best practices for customer messaging and stock balancing.

Quick Start

Use the multi-warehouse skill to allocate an order to the nearest available locations, create per-location fulfillment records, and reserve inventory accordingly.

Frequently Asked Questions about multi-warehouse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route orders to the optimal fulfillment location across multiple warehouses?

Multi-warehouse order routing uses a proximity-first scoring system to allocate orders to the nearest available location, prioritizing single-location fulfillment to minimize shipping costs and split shipments.

What is the best way to handle split shipments when no single warehouse has enough inventory?

When no single location can fulfill an order, a greedy split fallback assigns items to the nearest locations with available stock and generates one fulfillment record per location.

How does transfer order lifecycle management work for moving inventory between locations?

Transfer order management creates, ships, and receives inventory transfers, adjusting reserve and on_hand quantities atomically with partial receipt support and in-transit upsert semantics.

Does this multi-warehouse allocation approach work with Shopify, BigCommerce, and WooCommerce?

Multi-warehouse allocation supports Shopify, BigCommerce, WooCommerce with plugins, and custom headless platforms by providing step-by-step setup notes and platform-specific inventory routing guidance.

Why does multi-warehouse fulfillment routing prefer single-location fulfillment over split shipments?

Single-location fulfillment is preferred to minimize split shipments and shipping costs, falling back to greedy split allocation only when proximity scoring confirms no single location has sufficient stock.