omnichannel-fulfillment-allocator
Integrated fulfillment allocation skill for unified inventory across channels with intelligent order routing
Best use case
omnichannel-fulfillment-allocator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Integrated fulfillment allocation skill for unified inventory across channels with intelligent order routing
Teams using omnichannel-fulfillment-allocator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/omnichannel-fulfillment-allocator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How omnichannel-fulfillment-allocator Compares
| Feature / Agent | omnichannel-fulfillment-allocator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Integrated fulfillment allocation skill for unified inventory across channels with intelligent order routing
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Omnichannel Fulfillment Allocator
## Overview
The Omnichannel Fulfillment Allocator provides integrated fulfillment allocation for unified inventory across channels with intelligent order routing. It optimizes order assignment to fulfillment nodes, balances inventory across locations, and manages complex fulfillment scenarios including ship-from-store and buy-online-pickup-in-store (BOPIS).
## Capabilities
- **Distributed Order Management**: Orchestrate orders across multiple fulfillment nodes and channels
- **Store-Fulfillment Capability Scoring**: Rate stores for fulfillment suitability based on capacity, inventory, and performance
- **Inventory Promise/ATP Calculation**: Calculate accurate available-to-promise across all inventory locations
- **Ship-From-Store Optimization**: Optimize selection of stores for e-commerce fulfillment
- **BOPIS Order Orchestration**: Manage buy-online-pickup-in-store orders including inventory reservation and pickup scheduling
- **Split Shipment Optimization**: Determine optimal split shipment strategies balancing cost and customer experience
- **Channel Priority Balancing**: Balance fulfillment priorities across channels based on business rules
## Tools and Libraries
- OMS APIs
- Inventory Visibility Platforms
- Order Routing Engines
- Real-Time Inventory Systems
## Used By Processes
- Multi-Channel Fulfillment
- Distribution Network Optimization
- Last-Mile Delivery Optimization
## Usage
```yaml
skill: omnichannel-fulfillment-allocator
inputs:
order:
order_id: "ORD-2026-12345"
channel: "ecommerce"
customer_location: "Boston, MA"
delivery_type: "ship_to_home"
requested_delivery: "2026-01-27"
items:
- sku: "SKU001"
quantity: 2
- sku: "SKU002"
quantity: 1
fulfillment_nodes:
- node_id: "DC001"
type: "distribution_center"
location: "Newark, NJ"
inventory:
SKU001: 500
SKU002: 200
ship_cost_to_customer: 8.50
transit_days: 2
- node_id: "STORE042"
type: "store"
location: "Cambridge, MA"
inventory:
SKU001: 5
SKU002: 3
fulfillment_capability_score: 85
ship_cost_to_customer: 6.00
transit_days: 1
allocation_rules:
prefer_single_shipment: true
max_split_shipments: 2
protect_store_inventory_percent: 20
outputs:
fulfillment_allocation:
order_id: "ORD-2026-12345"
allocation_type: "single_shipment"
fulfillment_node: "STORE042"
node_type: "store"
shipments:
- shipment_id: "SHP001"
node: "STORE042"
items:
- sku: "SKU001"
quantity: 2
- sku: "SKU002"
quantity: 1
ship_cost: 6.00
estimated_delivery: "2026-01-26"
total_ship_cost: 6.00
customer_delivery_date: "2026-01-26"
allocation_rationale:
- "Store fulfillment selected for faster delivery (1 day vs 2 days)"
- "Store inventory sufficient after protection threshold"
- "Lower shipping cost ($6.00 vs $8.50)"
inventory_impact:
STORE042:
SKU001: { before: 5, after: 3, protected: 1 }
SKU002: { before: 3, after: 2, protected: 1 }
```
## Integration Points
- Order Management Systems (OMS)
- Warehouse Management Systems (WMS)
- Point of Sale Systems
- Inventory Management Systems
- E-commerce Platforms
## Performance Metrics
- Order fill rate
- Ship-from-store percentage
- Split shipment rate
- Fulfillment cost per order
- Delivery promise accuracyRelated Skills
Memory Allocator
Expert skill for custom memory allocator design optimized for language runtime needs
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.