Enterprise · EE1
Partner Channel Commerce EE1.3 · Intelligent order routing
Mocked data

Routing decisions

Auditable per-order routing. Engine is deterministic — no LLM in the decision path. Manual overrides require a reason.

Active routing rules

  1. Filter to partners with stock for the SKU.
  2. Filter to partners within geographic radius of customer.
  3. Filter to partners with capacity < 90% utilization.
  4. Tie-break by capacity-balanced round-robin (lowest current load wins).
  5. If no partner qualifies, route to manufacturer-direct fulfillment.

Rules are configurable at apps/admin /ee1 → Routing Rules. FeedAmp documented as a real implementation option.

Recent decisions

ORD-12847
Acme Industrial · Newark, NJ · 5/8/2026, 2:32:11 PM
SKU
MOTOR-3HP-EM-2026
Routed to
✓ Hooli Tools — Northeast
Other candidates considered
  • ✗ Globex Manufacturing — Out of stock
  • ✗ Initech Distribution — Geographic mismatch (1450mi)
Rationale

Closest partner with stock + capacity available. Distance: 8mi.

ORD-12848
Globex Manufacturing · Hartford, CT · 5/8/2026, 2:18:22 PM
SKU
BEARING-639-2RS
Routed to
✓ Globex Manufacturing
Other candidates considered
  • ✗ Hooli Tools — Northeast — Capacity at 95% (round-robin balancing)
Rationale

Capacity-balanced round-robin selected Globex (current capacity 67%) over Hooli (95%).

ORD-12849
Initech Distribution · San Francisco, CA · 5/8/2026, 1:55:08 PM
SKU
COATING-ZINC-1L
Routed to
✓ Initech Distribution
Rationale

Manual override: customer-dealer relationship (Initech is also a partner, fulfilling internal demand).

Routing decisions stored in paradigm-api-d1.routing_decisions. Triggered by BC store/order/created webhook. Engine is deterministic; LLM is not in the decision path.