<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Move stock across the network, wave-plan the pick, ship with the carrier integrated.
Inter-warehouse transfer orders, wave planning by carrier cut-off and customer commitment, ASN generation, carrier integration for label printing and tracking — orchestrated on the same engine that allocates the customer order.
Transfer orders
Inter-warehouse moves with the same documentation discipline as customer orders. Source pick, in-transit, destination receipt — each step journalled.
Wave planning
Picks waved against carrier cut-offs and customer-commitment dates. The operations team works waves, not orders.
ASN generation
Advance shipment notice in the format the customer's ERP expects — EDI, XML, PEPPOL — emitted from the same shipping confirmation.
Carrier integration
Label printing, manifest generation, tracking-number capture — integrated with the major Spanish and LATAM carriers and global parcel networks.
What the shipping surface covers
Transfer order types
Standard transfer, stock-balancing transfer, expiry-driven transfer (move near-expiry stock to higher-velocity location), customer-promise-driven transfer (consolidate to ship once).
Wave planning
Operations team composes waves by carrier cut-off, customer promise, picker route. The wave is the unit of work; orders are the unit of commercial commitment.
Pick confirmation
Mobile pick confirmation with barcode and weight validation. Discrepancies between picked and ordered routed to the supervisor, not silently shipped.
Shipping documents
Packing list, ASN, customs documents (where international), proof-of-delivery template — generated from the shipment record.
Carrier APIs
Label and tracking APIs with major carriers; manifest export for those without; rate-shopping where multiple carriers are configured.
Delivery tracking
Tracking-number capture against the shipment, delivery-confirmation API ingestion, exception management for failed deliveries.
Why the wave is the unit of work, not the order
An operations team that picks orders one at a time, in the sequence they arrive, is optimising for nothing — not picker route, not carrier cut-off, not customer promise. The result is duplicated walking, missed cut-offs and orders that ship later than promised because the pick happened in arbitrary order.
Axional's wave engine composes the work around constraints the operations team chooses — customer commitment first, carrier cut-off second, picker route third. The wave is released; the order is shipped as a consequence. The KPI that matters — on-time delivery — falls out of the discipline.