Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

multi-warehouse多仓库

Agent Skill

multi-warehouse 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

652

周安装

28

GitHub Stars

19

下载量

228
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:multi-warehouse(多仓库)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/multi-warehouse
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill multi-warehouse
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill multi-warehouse

简介

用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 使用时不能把工具输出直接当最终结论,需人工复核关键信息。

SKILL.md

Multi-Warehouse Inventory

Overview

Multi-warehouse inventory lets you stock products at multiple physical locations — warehouses, stores, 3PLs — and route each order to the location best positioned to fulfill it. Shopify and BigCommerce have multi-location inventory built in. WooCommerce needs a plugin. Only build a custom allocation engine if your routing logic (zone-based, cost-optimized, split fulfillment) exceeds what platform tools support.

When to Use This Skill

  • When a merchant operates more than one warehouse, store, or 3PL (third-party logistics) provider
  • When shipping cost is significant and routing orders from the nearest warehouse matters
  • When stock imbalance between locations requires transfer orders to redistribute inventory
  • When orders must sometimes be split across two warehouses because no single location has all items

Core Instructions

Step 1: Determine platform and choose the right tool

PlatformBuilt-in Multi-LocationRecommended Extension
ShopifyYes — up to 1,000 locations (Basic: 4, Shopify plan: 5, Advanced: 8)ShipBob or Flexport for 3PL fulfillment routing; ShipHero for advanced routing rules
WooCommerceNo — requires a pluginATUM Multi-Inventory (add-on) or WooCommerce Multi-Location Inventory by Iconic
BigCommerceYes — Multi-Location Inventory app (free)ShipStation for advanced routing; Whiplash or ShipBob for 3PL integration
Custom / HeadlessBuild allocation engine with proximity-first routingRequired when no platform tools meet routing and split-fulfillment requirements

Step 2: Platform-specific setup


Shopify

Shopify has native multi-location inventory.

Set up locations:

  1. Go to Settings → Locations → Add location
  2. Add each warehouse, store, or fulfillment center
  3. Enter the address (used for shipping rate calculation)
  4. Assign products to each location — go to a product, click a variant, and set the quantity at each location

Configure fulfillment routing:

  1. Go to Settings → Shipping and delivery → Shipping
  2. Under Fulfillment from, set the priority order for your locations
  3. Shopify routes orders to the first location in your priority list that has stock for all items
  4. For more sophisticated routing (proximity-based, cost-optimized): install ShipHero or ShipBob from the App Store

Transfer orders between locations:

  1. Go to Inventory → Transfers → Create transfer
  2. Select the Origin location (where stock is coming from)
  3. Select the Destination location
  4. Add the products and quantities to transfer
  5. When goods arrive, go to Transfers → [Transfer] → Accept items — Shopify automatically increments the destination and decrements the origin

3PL integration:

  • For ShipBob: Install ShipBob from the App Store; ShipBob pulls orders from Shopify and routes to the nearest fulfillment center automatically
  • For Flexport: Install the Flexport app; products and inventory sync bi-directionally

WooCommerce

WooCommerce requires a plugin for multi-location inventory.

Option A: ATUM Multi-Inventory (recommended)

  1. Install ATUM Inventory Management for WooCommerce (free core) + ATUM Multi-Inventory add-on (paid)
  2. In ATUM, go to Multi-Inventory → Locations → Add Location
  3. For each product, go to the ATUM Multi-Inventory tab and assign quantities per location
  4. Configure inventory selection rule (region-based, priority-based, or first-available)

Option B: WooCommerce Multi-Location Inventory by Iconic

  1. Install the plugin
  2. Go to WooCommerce → Multi-Location Inventory → Locations and add your warehouses
  3. Edit each product and set per-location stock quantities
  4. Configure fulfillment routing in the plugin settings

Transfer orders:

  • ATUM Multi-Inventory includes a transfer order feature — go to ATUM → Inventory Transfers → New Transfer
  • Set origin, destination, products, and quantities
  • Mark as received to update stock automatically

BigCommerce

BigCommerce supports multi-location inventory via a free app.

Enable Multi-Location Inventory:

  1. Go to Apps → Search "Multi-Location Inventory"
  2. Install and launch the app
  3. Add locations: Locations → Add location with name and address
  4. Assign stock per product per location

Configure fulfillment routing:

  1. In the Multi-Location Inventory app, go to Routing Rules
  2. Set rules: ship from nearest, ship from cheapest, ship from location with most stock, etc.
  3. BigCommerce generates split shipments automatically when an order can't be fulfilled from a single location

For 3PL integration:

  • Install ShipStation from the BigCommerce App Marketplace
  • ShipStation connects to your 3PL providers and routes based on your rules

Custom / Headless

For headless storefronts, build an allocation engine that selects the best location(s) for each order:

// lib/allocation.ts
import { haversineDistance } from './geo';

interface OrderItem { variantId: string; quantity: number; productName: string; }
interface AllocationResult {
  type: 'single' | 'split';
  fulfillments: { locationId: string; items: OrderItem[] }[];
}

export async function allocateOrder(orderItems: OrderItem[], shippingAddress: Address): Promise<AllocationResult> {
  const locations = await db.locations.findMany({ where: { active: true } });

  // Fetch inventory availability for all required variants at all locations
  const inventory = await db.inventoryLevels.findMany({
    where: { variantId: { in: orderItems.map(i => i.variantId) } },
  });
  const invMap = buildInventoryMap(inventory); // locationId -> variantId -> available

  // Score locations by distance to shipping address (proximity-first routing)
  const scored = locations
    .map(loc => ({
      ...loc,
      distanceKm: haversineDistance({ lat: loc.lat, lng: loc.lng }, { lat: shippingAddress.lat, lng: shippingAddress.lng }),
    }))
    .sort((a, b) => a.distanceKm - b.distanceKm);

  // Prefer single-location fulfillment to avoid split shipments
  for (const location of scored) {
    const canFulfillAll = orderItems.every(item => (invMap[location.id]?.[item.variantId] ?? 0) >= item.quantity);
    if (canFulfillAll) return { type: 'single', fulfillments: [{ locationId: location.id, items: orderItems }] };
  }

  // Fall back to split fulfillment — greedy assignment to nearest location with stock
  const remaining = [...orderItems];
  const fulfillments: AllocationResult['fulfillments'] = [];

  for (const location of scored) {
    const canFulfill = remaining.filter(item => (invMap[location.id]?.[item.variantId] ?? 0) >= item.quantity);
    if (canFulfill.length > 0) {
      fulfillments.push({ locationId: location.id, items: canFulfill });
      canFulfill.forEach(item => remaining.splice(remaining.findIndex(r => r.variantId === item.variantId), 1));
    }
    if (remaining.length === 0) break;
  }

  if (remaining.length > 0) throw new Error('Cannot fulfill order — insufficient stock across all locations');
  return { type: 'split', fulfillments };
}

// Transfer order management
export async function receiveTransferOrder(transferOrderId: string, receivedItems: { variantId: string; quantity: number }[]) {
  const transfer = await db.transferOrders.findUnique({ where: { id: transferOrderId }, include: { items: true } });

  await db.$transaction([
    // Decrease on_hand + reserved at source
    ...receivedItems.map(item => db.inventoryLevels.update({
      where: { variantId_locationId: { variantId: item.variantId, locationId: transfer.fromLocationId } },
      data: { onHand: { decrement: item.quantity }, reserved: { decrement: item.quantity } },
    })),
    // Increase on_hand at destination
    ...receivedItems.map(item => db.inventoryLevels.upsert({
      where: { variantId_locationId: { variantId: item.variantId, locationId: transfer.toLocationId } },
      create: { variantId: item.variantId, locationId: transfer.toLocationId, onHand: item.quantity, reserved: 0 },
      update: { onHand: { increment: item.quantity } },
    })),
    db.transferOrders.update({ where: { id: transferOrderId }, data: { status: 'received' } }),
  ]);
}

Step 3: Configure split-shipment communication

When an order is split across two locations, customers must be informed before confirming their order.

Shopify: Shopify's native checkout shows "Ships from multiple locations" in the shipping options when a split is needed. Customize the messaging in Settings → Checkout → Checkout language.

WooCommerce: Display a notice in the cart/checkout when ATUM detects a split is needed. ATUM Multi-Inventory includes configurable messaging for split shipments.

In the order confirmation email: Include all fulfillment groups with their expected shipping dates. "Your order will arrive in 2 shipments" with item breakdowns reduces support tickets.


Step 4: Balance stock across locations

Chronic stock imbalances (one warehouse overstocked, another out of stock) increase transfer costs and split fulfillments. Run a weekly analysis:

Signs of imbalance:

  • One location consistently has the same SKU at zero while another has excess
  • More than 20% of orders require split fulfillment for the same SKU
  • Transfer requests for the same product direction repeat every week

Action: Create a transfer order from the overstocked location to the understocked one before the next reorder cycle.

Shopify Stocky: Shows an "Inventory distribution" report that identifies imbalanced SKUs across locations.

Best Practices

  • Prefer single-location fulfillment — split shipments increase cost and confusion; exhaust single-location options before splitting
  • Use platform-native multi-location before buying an app — Shopify and BigCommerce handle the common case well; only add apps when routing logic is more complex than what the platform supports
  • Model transfer orders as in-transit inventory — reduce available stock at the source when the transfer ships; don't increment the destination until goods arrive and are counted
  • Inform customers of split shipments at checkout, not after purchase — finding out after payment feels deceptive
  • Run stock-balancing analysis weekly — a 15-minute review of the distribution report prevents chronic imbalances that compound over time

Common Pitfalls

ProblemSolution
Split fulfillment creates two shipping chargesConsolidate shipping cost at the order level; absorb the second shipment cost or notify the customer during checkout — never charge twice silently
Transfer received quantity differs from sentSupport partial receipt — record the actual received quantity per item and handle discrepancies (damaged in transit) separately
Inventory double-counted across locationsEach inventory record is location-scoped; when reporting total stock, always sum across locations explicitly
Location goes offline mid-fulfillmentMark location as inactive; re-run allocation for unfulfilled orders assigned to that location
Customer confused about multiple tracking numbersSend a separate tracking email per fulfillment with a clear note: "This is shipment 1 of 2 for your order"

Related Skills

  • @inventory-tracking
  • @low-stock-alerts
  • @catalog-import-export

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.45%
按下载量换算83

Claude

28.48%
按下载量换算65

Cursor

15.87%
按下载量换算36

Gemini CLI

9.47%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills