AI EDI Rejection Recovery
Understand EDI rejections faster. Correct supported errors with confidence.
When a retailer rejects a shipping notice, your team loses time finding out why, and late or incorrect notices can lead to retailer charges.
AI EDI Rejection Recovery helps your team find the likely cause quickly, agree on the next action and resend supported corrections safely, with a person approving every correction.
It handles EDI 824 rejections of EDI 856 Advance Ship Notices (ASNs) in Celigo. For supported barcode errors, the correction is validated against your reference data before it is resent.
AI names the likely cause, the owner and the next action.
Code checks each barcode fix; a person approves it.
A case closes only when the retailer accepts the ASN.
A Successful Transmission Doesn’t Mean Your ASN Was Accepted
Your EDI platform may report that a shipment notice was sent successfully. But the retailer can reject it later.
Your team then has to identify the issue, investigate the data, determine the correct action, and confirm whether the retailer accepts the correction.
Teknuro helps organize that process with AI-assisted investigation and controlled recovery.
How it works
Four steps from the retailer’s rejection to its acceptance. AI investigates, code validates and a person approves.
Step 1 · Celigo
Receive
Receive the retailer’s EDI 824 rejection.
Step 2 · AI
Investigate
AI examines the rejection and available reference data to identify likely causes and recommend next actions.
Step 3 · Rules and reviewer
Validate & Approve
Deterministic checks validate supported barcode corrections. A named reviewer approves the proposed revision.
Step 4 · Celigo
Resend & Monitor
Send the corrected ASN through the configured partner endpoint and monitor the retailer’s response.
Current correction scope
Version 1.1 supports validated corrections to the LIN03 barcode field in EDI 856 ASNs. Other rejection types receive guided investigation rather than automatic correction.
AI Investigates. Validation Rules Protect the Process.
The AI agent analyzes the rejection and available evidence to explain the likely problem, identify missing information, and recommend an action.
Rules implemented in code determine whether a correction is allowed. AI cannot independently change shipping documents or authorize resubmission.
AI
Root Cause Analysis
Investigate whether the rejection relates to document data, source records, physical shipment information, or retailer requirements.
AI
Recommended Actions
Identify the next action, responsible team, and missing evidence.
Rules and reviewer
Controlled Correction
Validate supported barcode corrections against the available reference data before human approval.
Adapt EDI Recovery to Your Trading Partners
Retailers can have different EDI rules, document requirements, and acceptance processes.
Teknuro can help configure retailer-specific profiles, adapt the integration to your VAN or B2B provider, and extend the workflow to support additional requirements.
Optional extensions, assessed per project (not included in version 1.1):
- Live ERP or warehouse lookups
- Additional correction types
- A dedicated approval interface
See How Rejection Recovery Works
An illustrative walkthrough of one of the nine example cases that ship with the template. All data is fictional; this is a test scenario, not a customer result.
- Rejection. A fictional retailer rejects an ASN in an EDI 824: the barcode on line 2 is not accepted.
- AI investigation. The AI agent cites the evidence: the barcode on line 2 has been retired, and names the likely cause and the next action.
- Validation. Code checks the replacement barcode: the same item at the packaging level shipped, active on the ship date, on file with the retailer and scanned at dispatch. The fix gets a revision code.
- Approval. A named reviewer approves that exact revision in Celigo.
- Resend and acceptance. The corrected 856 is sent with an idempotency key, and the retailer’s acceptance closes the case.
Other example cases
Guided investigation
60 cases shipped, 48 ordered. No automatic fix: the warehouse is named as owner, the dispatch record is requested and the quantity is not changed.
Wrong fix refused
The same retired barcode, but the cartons carry the old one. Resending would contradict the goods, so it is refused.
Evidence arrives later
The dispatch record is missing, so the case waits. When it arrives, the new revision is approved and sent.
Requirements & Technical Details
What you need in place, and how version 1.1 behaves.
- Celigo integrator.io with AI Agents and Guardrails. Each diagnosed rejection uses Celigo AI credits.
- Incoming EDI 824 forwarding: a VAN, AS2 service or Celigo B2B Manager flow that forwards each 824 to the webhook as JSON, with the webhook token in a request header.
- Reference data loaded into the included lookup cache: the 856s you sent, purchase orders, the item master with barcodes per packaging level, warehouse dispatch records and each retailer’s rules and item catalogue.
- Trading-partner profiles: one tested profile per retailer.
- An endpoint for corrected ASNs at your VAN or B2B provider. Tested format: JSON that contains the full X12 message.
Technical details
- Approval: in version 1.1, a reviewer approves by editing retry data in Celigo. No separate review screen is included.
- Lookups: no live ERP or WMS lookup is included; reference data is loaded by you.
- Acknowledgements: EDI 997 and 999 acknowledgements are not processed as recovery cases.
- Document type: only 824s about 856 ASNs are handled.
- Duplicates: the same 824 sent twice creates two cases with the same revision and idempotency key.
- Raw X12: sending raw X12 instead of JSON needs a one-line change that has not been tested.
- Updates: templates receive no automatic updates; every resource is yours to change after install.
- Safety rules: quantities, dates and lot numbers are never changed; an approval applies only to the exact revision; refused sends and unknown outcomes are told apart; only full acceptance closes a case.
- AI processing: the diagnosis runs on Claude by Anthropic through Celigo AI, with a fixed JSON output. The agent sees only the 824 and the evidence for that case; approver notes pass a Celigo PII guardrail.
- Security: the webhook accepts only requests that carry its token, credentials stay in the Celigo connection and all traffic uses HTTPS.
How to get started
From first contact to real traffic. The setup guide has the full steps.
Discuss a pilot
Email info@teknuro.com with your retailers and rejection volumes.
Get your license
Teknuro issues your license and tells you when it is ready.
Set it up
Connect your endpoint and 824 forwarding, and add retailer profiles.
Test and go live
Run the demo data and nine test 824s, then load your own data.
Availability, pricing and support
Release readiness
Version 1.1 was built and tested in Teknuro’s Celigo sandbox with demo data. On 23 October 2026, fresh installations from the release package ran all nine test cases end to end against a test endpoint.
It has not yet been used in a customer production environment, and there are no pilot results yet. The planned pilot replays 50 to 100 past rejections from one ERP and one or two retailers.
Pricing and licensing
Pricing on request: info@teknuro.com
- Teknuro issues a license for your Celigo account and tells you when it is ready. Celigo Marketplace availability is confirmed on request.
- Not included: your Celigo integrator.io subscription, Celigo AI credits and Guardrails, and your VAN or B2B provider costs.
Support
- Email: info@teknuro.com
- Monday to Friday, 09:00–17:00 CET/CEST
- We reply within two business days.
- Send the case code from Celigo (for example SENT_OUTCOME_UNKNOWN), the flow step and the time it happened. Do not email EDI documents or personal data; we will arrange a secure channel if we need them.
Documentation
- Setup guide: install, partner profiles, archive data, decisions and result codes, limits
- Step-by-step test guide
- White paper (PDF)
All three are available on request at info@teknuro.com.
Built by Teknuro on Celigo integrator.io. Celigo and integrator.io are trademarks of Celigo, Inc. Claude is a trademark of Anthropic.
ASN rejections every week?
Discuss an EDI rejection recovery pilot. We will walk through the nine test cases with your own rejection patterns in mind and scope a replay of 50 to 100 past rejections. We reply within two business days.
