Integrations
/ WMS
/ Körber WMS (HighJump)
Integrations · Warehouse management (WMS)
TracePharma + Körber WMS (HighJump)
TracePharma receives ship-confirm callbacks from Körber WMS (HighJump) and normalizes them into outbound EPCIS shipment drafts—without replacing your WMS.
Preset:
korber
HTTPS webhook
Körber WMS (HighJump) continues to drive pick/pack/ship. TracePharma is your L4 hub. Ship-confirm webhooks trigger EPCIS generation, ACK monitoring, and exception workflows when customer GLNs or serial data are missing.
Inbound interoperability
- ✓ POST /api/webhooks/wms/{tenantId}/korber/ship-confirm with ship-confirm JSON payload.
- ✓ Optional X-Korber-Secret shared-secret authentication.
- ✓ Payload customer GLN matched to authorized trading partners before queue.
Outbound & compliance
- ✓ Outbound EPCIS documents generated from normalized ship-confirm data.
- ✓ Optional auto-queue for partner delivery after validation.
- ✓ wms_ship_confirm_events audit with operations scorecard blocked-reason trends.
Typical cutover steps
- 1 Enable WMS ship-confirm integration in Tenant Settings.
- 2 Configure shared secret for Körber WMS (HighJump) if required.
- 3 Point WMS middleware at your tenant ship-confirm webhook URL.
- 4 Ensure customer GLN in payload matches a trading partner record.
Best for
- → Regional wholesalers and 3PLs running Körber WMS (HighJump).
- → DC teams that want EPCIS outbound triggered from WMS ship-confirm—not manual re-entry.
- → Operations leads monitoring blocked ship-confirms on the operations scorecard.
Körber WMS (HighJump) interoperability FAQ
- Does TracePharma replace Körber WMS (HighJump)?
- No. Körber WMS (HighJump) remains your WMS. TracePharma consumes ship-confirm events and produces DSCSA-compliant outbound EPCIS.
Connect Körber WMS (HighJump) in your tenant
We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.