Receive structured customer or partner demand.
Accept supported orders, forecasts, releases, transfers, appointments, or replenishment messages and route them through controlled validation and review.
AJAX Electronic Data Interchange
Exchange business documents backed by operational truth.
AJAX EDI connects customer, supplier, carrier, grower, and trading-partner documents to the same orders, pallets, lots, loads, inspections, images, signatures, exceptions, and Business Central records used by the operation.
Execution-Connected Documents
Build document exchange around the work that actually happened.
Document creation, validation, exchange, acknowledgment, exception review, and final proof can remain tied to the source transaction instead of being rebuilt from separate warehouse screens, emails, spreadsheets, carrier portals, and paper records.
Return approved order status and changes.
Generate acknowledgments, confirmations, changes, substitutions, shortages, dates, quantities, and partner references from validated operational and ERP data.
Build shipment detail from actual picked inventory.
Connect orders, loads, SSCCs, pallets, lots, quantities, packaging, labels, dates, carrier data, and shipment milestones to the outbound notice.
Keep financial messages aligned with approved results.
Use Business Central invoices, credits, returns, shipments, claims, deductions, taxes, and financial references where partner flows require them.
Connect tender, shipment, and delivery messages.
Exchange supported load tenders, responses, appointments, shipment status, route milestones, delivery proof, and freight documents with approved partners.
Find missing or inconsistent data before transmission.
Validate identifiers, quantities, dates, addresses, units, lots, SSCCs, references, and required partner fields before sending.
Track receipt and technical acceptance.
Preserve 997, 999, TA1, and other supported technical acknowledgment status without treating those technical acknowledgments as additional billable business documents.
Route failures to people who can resolve them.
Surface mapping errors, missing data, rejected messages, quantity differences, late documents, duplicates, unacknowledged messages, and partner-specific issues.
Document Lifecycle
One controlled path from source event to partner acceptance.
The same partner, transaction type, source document, order, shipment, pallet, lot, invoice, acknowledgment, exception, retry, and final status can remain connected through the complete EDI lifecycle.
Start from a partner message, approved ERP document, warehouse event, load milestone, delivery proof, or configured schedule.
Check identifiers, required fields, data types, quantities, dates, references, and supporting status.
Map AJAX OES and Business Central data into the agreed partner format, version, and transaction structure.
Send or receive through the configured connection and preserve transmission, direction, retry, and error history.
Track technical and business acknowledgment status, partner acceptance, rejection, and required follow-up.
Review exceptions, correct approved data, resend when permitted, and keep the final document tied to its proof.
Configurable Partner Control
Apply different document, validation, timing, transport, and proof rules by partner.
Customers, suppliers, growers, carriers, marketplaces, and integration partners may require different identifiers, standards, versions, timing, labels, acknowledgments, and connection methods.
Connect order, shipment, invoice, and proof flows.
Support customer-specific demand, acknowledgment, shipment, delivery, return, claim, deduction, and financial document requirements.
Connect inbound commitments and receiving results.
Support purchase, contract, shipment, receiving, grade, claim, settlement, or supporting-document exchange where configured.
Connect tender, load status, and delivery evidence.
Exchange supported tender, response, appointment, tracking, temperature, proof, exception, invoice, and delivery data with approved partners.
Rules by Trading Relationship
Configure identifiers, mapping, transport, timing, security, and exception requirements for each partner relationship.
| Rule Area | Partner Configuration |
|---|---|
| Partner | Configure sender, receiver, account, location, customer, supplier, grower, carrier, and routing identifiers. |
| Transaction | Define supported inbound and outbound document types, standards, versions, required fields, and business rules. |
| Timing | Trigger immediately, on approval, on schedule, after posting, after loading, or after delivery proof. |
| Validation | Require references, lot detail, SSCCs, quantities, labels, addresses, proof, or financial status. |
| Exception | Route rejected, late, duplicate, incomplete, mismatched, retried, or unacknowledged messages into review. |
Document Control and Exception Proof
Trace every exchanged document back to its source.
Transmission status alone does not explain what happened. AJAX EDI is designed to preserve the source document, operational evidence, mapping result, acknowledgment, exception, correction, and retry history together.
Document Control Center
Review the complete exchange status.
Review partner, transaction, direction, source record, created time, transmission status, acknowledgment, validation result, and current exception state.
Exception Review With Operational Proof
Compare the failed document with the actual work.
Compare the rejected or incomplete document with the actual order, SSCC, lot, load, image, signature, inspection, shipment event, and delivery evidence.
Connected Operations
EDI becomes more reliable when warehouse, logistics, quality, finance, and profitability share the same source records.
AJAX OES applications are designed to preserve the relationship between the exchanged business document and the operational or financial event that created it.
Received, serialized, allocated, picked, staged, loaded, counted, corrected, and shipped inventory can support order and ASN detail.
View WMSCarrier, tender, appointment, dock, load, route, departure, temperature, delivery, signature, and exception data can support transportation exchange.
View LogisticsAudit results, holds, releases, grades, photos, certificates, claims, and disposition evidence can be connected to exchanged documents.
View QMSBusiness-document volume, partner complexity, manual correction, chargebacks, claims, and customer-specific requirements can support cost-to-serve analysis.
View Profitability
Business Central Connection
Keep Business Central as the financial system of record while AJAX OES manages document execution and operational proof.
Business Central can provide authorized customer, vendor, item, order, receipt, shipment, return, invoice, credit, tax, and financial references while AJAX OES contributes the operational execution and evidence required by the partner flow.
Validate, transform, exchange, monitor, and reconcile.
AJAX OES can manage supported business documents while preserving their relationship to warehouse, quality, logistics, grower, and delivery records.
Use governed partner and product definitions.
Customers, vendors, items, units of measure, locations, addresses, dimensions, and partner identifiers remain connected.
Connect exchange to the source transaction.
Purchases, sales, transfers, returns, receipts, warehouse shipments, production, and posted shipment references remain available.
Use approved financial results.
Invoices, credits, taxes, deductions, claims, payment references, and posted financial results remain connected.
Connect only to authorized environments and partners.
Each AJAX OES tenant connects only to its authorized Business Central environments, companies, and configured trading relationships.
Transparent Usage
Estimate EDI usage by the business documents successfully sent or received.
AJAX EDI pricing separates the recurring application fee from measurable document activity. The current public pricing estimator uses successful business documents sent or received as the EDI usage driver.
Count each successfully sent business document once.
Examples may include acknowledgments, confirmations, advance ship notices, invoices, credits, status documents, tenders, and other supported partner messages.
Count each successfully received business document once.
Examples may include orders, releases, forecasts, tender responses, claims, shipment information, and other supported partner documents.
Do not count technical responses as separate business documents.
Technical acknowledgments such as 997, 999, and TA1 are included at no additional charge and are not counted as separate billable business documents. Failed validations, unsuccessful transmissions, retries, testing traffic, and partner-specific edge cases are governed by the applicable service configuration and commercial terms.
Executive Value
Reduce manual reconstruction, chargeback risk, and disconnected integration tools.
Connected source records give operations, integration, finance, and service teams one document history for exchange, exception, evidence, and commercial review.
Teams spend less time rebuilding order, receipt, shipment, load, delivery, and financial information from separate systems and paper.
SSCCs, lots, scans, photos, signatures, inspections, timestamps, load history, and delivery evidence remain connected.
Validation, acknowledgment, retry, correction, ownership, and final status provide a clearer path to resolution.
Required identifiers, quantities, dates, references, labels, SSCCs, shipment detail, and proof can be reviewed before transmission.
Document volume, mapping requirements, exceptions, corrections, claims, and manual support can help explain customer and sales-order cost.
Shared source records reduce repeated explanations, disconnected logs, and conflicting versions of partner status.
Start with connected business-document exchange.
Estimate AJAX OES pricing, create a tenant, and begin guided setup without waiting for a consultation.
Partner and Standards Dependency
AJAX EDI capabilities shown on this page describe the intended integration application and may include planned features.
Final availability and scope depend on partner requirements, supported standards and versions, connection methods, external providers, security approval, Business Central configuration, mapping, testing, certification, transaction volume, enabled applications, and implementation. Successful exchange also depends on trading-partner participation and data quality.