.png)
TrueCommerce Integration Guide
Connect TrueCommerce trading-partner and EDI exchanges with ERP, commerce, warehouse, and logistics systems through APIs, secure file transfer, and orchestrated workflows.
TrueCommerce integration options at a glance
TrueCommerce integrations commonly use EDI and secure file exchange, including SFTP, AS2, managed network services, and structured X12 or EDIFACT documents. Some TrueCommerce offerings also provide REST API access, although the exact endpoint, resources, authentication, pagination, and limits depend on the provisioned product. Callback or notification support may be available for selected services, but universal webhook coverage is not confirmed. Martini can receive files or API payloads, validate and transform transactions, apply partner-specific rules, route documents to enterprise applications, and generate outbound acknowledgements or EDI files. Credentials, certificates, and channel settings remain environment-specific configuration.
| Integration point | Supported by TrueCommerce? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Limited | Some TrueCommerce product offerings provide API-oriented integration for retrieving or submitting transaction data. The relevant base URL, resources, authentication, pagination, and limits must be confirmed for the customer’s service. | Martini can consume the provisioned TrueCommerce REST API, map responses into canonical models, call downstream systems, and manage workflow-level retries and status tracking. |
| File import/export and EDI | Yes | Structured X12 or EDIFACT files and partner-specific layouts are central to TrueCommerce exchanges. Files may be delivered through managed services or secure transfer channels. | Martini can orchestrate file pickup, parsing, validation, transformation, routing, archival, quarantine, and outbound document generation when the required transport is available. |
| SFTP | Yes | SFTP may be used for secure inbound and outbound EDI or structured file exchange, including batch-oriented transaction delivery. | Martini can coordinate secure file ingestion and delivery, temporary and processed directories, duplicate detection, failed-file quarantine, and retention workflows. |
| AS2 | Yes | AS2 may be used for EDI transport with encryption, signing, certificates, and receipt acknowledgements. | Martini can orchestrate document processing around the configured AS2 arrangement and keep transport, acknowledgement, and business-processing statuses distinct. |
| Webhooks and outbound callbacks | Limited | Selected TrueCommerce services may expose callbacks or notifications, but universal coverage for every EDI document and trading-partner event was not verified. | Martini can expose a controlled API endpoint to receive confirmed callbacks and start workflows; scheduled polling or file ingestion remains the fallback when callbacks are unavailable. |
| Bulk, asynchronous, and batch processing | Limited | Batch processing is common for EDI and file exchange, while a general public TrueCommerce bulk or asynchronous API specification was not verified. | Martini can process grouped files or transaction batches with checkpoints, per-document validation, correlation, retry, and reconciliation logic. |
| Authentication and secure transport | Limited | Authentication depends on the provisioned product and channel and may involve API credentials, secure file-transfer credentials, AS2 certificates, HTTPS, or other secure transport settings. | Martini stores environment-specific credentials and certificates outside workflow logic and applies the configured authentication and transport requirements to each integration path. |
| GraphQL APIs | Not confirmed | No official TrueCommerce GraphQL documentation was verified, so GraphQL should not be assumed for this integration. | Martini can consume GraphQL when a provider documents and provisions it, but the TrueCommerce integration should use confirmed APIs or transport mechanisms instead. |
How TrueCommerce exposes data and business events
TrueCommerce REST APIs
TrueCommerce supports API-oriented integration in some product offerings and scenarios. A single public API specification for the complete platform was not verified, so endpoint availability, resources, authentication, pagination, rate limits, and payload sizes must be confirmed for the provisioned service.
Martini implementation pattern
Martini implementation pattern: Martini consumes the confirmed TrueCommerce API from a workflow, stores credentials in environment configuration, retrieves or submits transactions, maps the payload to a canonical model, and records provider and business statuses for reconciliation.
Implementation sequence
TrueCommerce EDI and file exchange
EDI and secure file exchange are central TrueCommerce integration mechanisms. Transactions may use X12, EDIFACT, partner-specific layouts, SFTP, AS2, managed network services, or other configured transport arrangements.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves the file, preserves the original payload or file reference, parses and normalizes the document, applies partner-specific validation and mapping, routes the transaction, and produces acknowledgements or outbound files through the configured channel.
Implementation sequence
TrueCommerce callbacks and notifications
Some TrueCommerce services may provide callbacks or notification capabilities for selected products or event types, but universal webhook coverage for all EDI transactions was not verified. File exchange or scheduled polling may be required instead.
Martini implementation pattern
Martini implementation pattern: When a confirmed callback is available, Martini exposes a controlled API endpoint, authenticates and validates the notification, retrieves the current transaction when necessary, and starts a workflow. The same workflow can be invoked by a scheduler or file trigger when callbacks are unavailable.
Implementation sequence
TrueCommerce batch processing
Batch-oriented processing is common for EDI and file exchange, although a general public TrueCommerce bulk API specification was not verified. Grouped files should be treated as batches rather than assumed to be REST bulk requests.
Martini implementation pattern
Martini implementation pattern: Martini schedules or triggers batch pickup, separates individual documents, processes each transaction with independent validation and idempotency controls, and produces a batch-level reconciliation result without losing document-level failures.
Implementation sequence
Common TrueCommerce integration patterns
Pattern 1: Synchronize purchase orders and invoices with an ERP
When to use this pattern
Use this pattern when TrueCommerce exchanges purchase orders, invoices, acknowledgements, and shipment updates with an ERP such as SAP S/4HANA, Oracle NetSuite, or Microsoft Dynamics 365.
Integration direction
Example Mapping
| TrueCommerce Field | Canonical Field | Target Field |
|---|---|---|
| Purchase order number | orderNumber | Sales order or purchase order number |
| Trading partner identifier | partnerId | Customer or supplier account |
| Requested delivery date | requestedDeliveryDate | Requested receipt or delivery date |
| Invoice total | invoiceTotal | Document total |
Martini implementation pattern
Martini receives the transaction through a confirmed API, file, SFTP, AS2, or managed exchange channel, identifies the trading partner, and applies the correct document mapping. It validates required fields and totals before writing to the ERP, stores control numbers and target identifiers for idempotency, and transforms ERP acknowledgements, shipment updates, or invoices back into the required TrueCommerce format. Failed documents are retained for replay without creating duplicate business records.
Martini capabilities used
- workflows
- API consumption
- file and payload processing
- data mapping
- business rules
- error handling
- idempotency and reconciliation
Pattern 2: Route commerce orders into EDI fulfillment
When to use this pattern
Use this pattern when Shopify or Adobe Commerce orders must be converted into TrueCommerce trading-partner transactions and shipment or order-status updates must be returned to the commerce platform.
Integration direction
Example Mapping
| TrueCommerce Field | Canonical Field | Target Field |
|---|---|---|
| Commerce order ID | orderNumber | Purchase order or partner order reference |
| SKU | itemCode | Partner item identifier |
| Shipping address | shipToAddress | EDI ship-to address segments |
| Fulfillment status | shipmentStatus | Shipment or ASN status |
Martini implementation pattern
Martini consumes commerce orders, enriches them with trading-partner, SKU, unit-of-measure, and shipping rules, and generates the required TrueCommerce EDI or structured file. It validates address, line, and quantity data before transmission. Inbound shipment confirmations are correlated to the commerce order and transformed into status updates, while rejected or duplicate transactions are routed to an operational queue for controlled replay.
Martini capabilities used
- workflows
- API consumption
- data mapping
- code conversion
- business rules
- scheduled or event-driven execution
- error handling
Pattern 3: Generate retailer ASNs from warehouse shipments
When to use this pattern
Use this pattern when retailer purchase orders arrive through TrueCommerce and warehouse or ERP shipment data must be converted into advance shipment notifications and related documents.
Integration direction
Example Mapping
| TrueCommerce Field | Canonical Field | Target Field |
|---|---|---|
| Purchase order number | orderNumber | Warehouse order reference |
| Package or carton identifier | packageId | ASN package or container identifier |
| Carrier tracking number | trackingNumber | Shipment tracking reference |
| Shipped quantity | quantityShipped | ASN item quantity |
Martini implementation pattern
Martini receives and validates the retailer purchase order, sends the normalized order to the warehouse or ERP, and waits for shipment and carrier data. It enriches the shipment with package, tracking, and item details, applies retailer-specific ASN rules, and generates the outbound TrueCommerce document. Ordering differences are handled with correlation keys and reconciliation rather than assuming documents arrive sequentially.
Martini capabilities used
- workflow orchestration
- data mapping
- business rules
- conditional routing
- correlation
- error handling and retry
Pattern 4: Route multi-partner EDI transactions
When to use this pattern
Use this pattern when multiple retailers, suppliers, or distributors use different document layouts, qualifiers, code lists, and acknowledgement requirements through TrueCommerce.
Integration direction
Example Mapping
| TrueCommerce Field | Canonical Field | Target Field |
|---|---|---|
| Trading partner identifier | partnerId | Routing configuration |
| EDI document type | documentType | Application transaction type |
| Partner item code | itemCode | Internal SKU |
| Control number | transactionControlNumber | Processing and acknowledgement reference |
Martini implementation pattern
Martini identifies the partner and document type, selects reusable transformation logic plus partner-specific rules, and routes normalized data to the appropriate ERP, warehouse, commerce, or finance application. Outbound responses are generated from the target result and delivered through the required TrueCommerce channel. Each transaction retains its original reference, validation outcome, downstream response, and replay state.
Martini capabilities used
- workflow orchestration
- partner-specific mappings
- routing
- data transformation
- validation
- business rules
- monitoring and replay
Applications commonly integrated with TrueCommerce
TrueCommerce commonly sits between trading partners and enterprise applications that manage orders, products, fulfillment, finance, and customer-facing commerce. The exact scope depends on the partner mappings and TrueCommerce services provisioned.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize purchase orders, sales orders, invoices, inventory, and shipment information with trading-partner exchanges. | TrueCommerce → Martini → SAP S/4HANA | Martini receives EDI files or API payloads, applies partner-specific mapping and validation, and writes canonical order or invoice data to SAP S/4HANA. Outbound acknowledgements, shipment updates, and invoices are transformed back into the required TrueCommerce document format. |
| Oracle NetSuite | Exchange orders, fulfillment updates, invoices, item data, and customer or supplier information with trading partners. | TrueCommerce → Martini → Oracle NetSuite | A Martini workflow polls or receives TrueCommerce transactions, normalizes X12, EDIFACT, or structured payloads, and calls NetSuite endpoints. Response statuses and business identifiers are retained for reconciliation and outbound document generation. |
| Microsoft Dynamics 365 | Connect orders, invoices, shipments, inventory, and trading-partner data with business applications. | TrueCommerce → Martini → Microsoft Dynamics 365 | Martini separates shared transformations from partner-specific rules, validates required fields and codes, and routes accepted documents to Microsoft Dynamics 365. Failed documents are quarantined with their original transaction identifiers for replay. |
| Salesforce | Synchronize account, order, service, or commerce-related information with EDI transaction status where Salesforce is part of the customer or commerce process. | TrueCommerce → Martini → Salesforce | Martini maps relevant trading-partner and transaction status data into Salesforce while keeping ERP and EDI document processing authoritative. Selective outbound updates can be exposed through a Martini API or workflow. |
| Shopify | Send commerce orders into fulfillment and EDI processes and return shipment or order-status updates. | Shopify → Martini → TrueCommerce | Martini receives Shopify order data, applies trading-partner and product-code mappings, and produces the required TrueCommerce EDI or file payload. Shipment confirmations from TrueCommerce or downstream systems are transformed back to Shopify. |
| Adobe Commerce | Convert online orders and catalog or inventory data into downstream fulfillment and trading-partner transactions. | Adobe Commerce → Martini → TrueCommerce | A workflow consumes Adobe Commerce data, enriches it with partner and item mappings, validates order totals and addresses, and sends the resulting document through the configured TrueCommerce channel. Rejections are recorded for operational review. |
| Microsoft Dynamics 365 Business Central | Exchange sales orders, purchase orders, invoices, inventory, and shipment data with trading partners. | Microsoft Dynamics 365 Business Central → Martini → TrueCommerce | Martini orchestrates bidirectional synchronization, correlates Business Central identifiers with EDI control numbers, and handles partner-specific code conversion, acknowledgements, retries, and duplicate detection. |
| Manhattan Active | Coordinate fulfillment, shipment confirmation, inventory, and advance shipment notification information. | TrueCommerce → Martini → Manhattan Active | Martini transforms retailer orders for warehouse processing, enriches shipment data with carrier and package details, and generates partner-specific ASN documents. Processing state and validation failures are retained for reconciliation. |
How to build a TrueCommerce integration in Martini
Objective
Confirm the TrueCommerce product, channel, endpoint, trading partners, document standards, and authentication requirements before building workflows.
Instructions in Martini
- Confirm whether the integration uses a REST API, SFTP, AS2, managed exchange, or another supported channel
- Store API credentials, file-transfer credentials, and certificates as environment configuration
- Document partner identifiers, document types, control numbers, and acknowledgement expectations
Objective
Select an event, file, API, or schedule trigger based on the TrueCommerce capabilities confirmed for the tenant and transaction types.
Instructions in Martini
- Use a confirmed callback or Martini API endpoint when the service provides notifications
- Use file pickup or scheduled polling when webhook coverage is unavailable
- Define polling intervals, batch windows, and concurrency limits
Objective
Retrieve or accept TrueCommerce transactions while preserving the original payload, file reference, and transport metadata needed for audit and replay.
Instructions in Martini
- Receive API payloads, EDI files, or structured documents through the configured channel
- Capture trading-partner identifiers, document types, control numbers, and provider references
- Archive the original input or a durable reference before transformation
Objective
Use a Martini workflow to coordinate parsing, validation, routing, downstream calls, acknowledgements, and status updates.
Instructions in Martini
- Separate transport status from technical processing and business acceptance status
- Route documents by partner, document type, and target application
- Use correlation keys when orders, shipments, invoices, and acknowledgements arrive out of sequence
Objective
Convert X12, EDIFACT, partner-specific files, or API payloads into canonical and target application models.
Instructions in Martini
- Normalize dates, decimals, units of measure, encodings, codes, and identifiers
- Keep shared transformations reusable and isolate partner-specific rules
- Generate outbound EDI or structured documents from validated target data
Objective
Prevent invalid or duplicate transactions and enforce partner-specific requirements before writing or transmitting business documents.
Instructions in Martini
- Validate required segments, fields, totals, addresses, item codes, and document relationships
- Use control numbers, purchase-order numbers, invoice numbers, and shipment identifiers for idempotency
- Apply acknowledgements, rejection, quarantine, and approval rules appropriate to each document type
Common TrueCommerce data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Trading Partners | Represent customers, suppliers, retailers, distributors, carriers, and other organizations participating in an exchange. | ERP, warehouse platforms, commerce applications, partner-management processes | Martini uses partner identifiers and configuration to select mappings, document rules, routing, code conversions, and validation requirements. |
| Orders | Represent order transactions exchanged between buyers, suppliers, retailers, and distributors. | SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365, Shopify, Adobe Commerce | Martini validates order identifiers and line data, transforms EDI or API payloads into target models, applies partner rules, and records processing status. |
| Purchase Orders | Represent buyer-originated orders, commonly exchanged through EDI purchase-order documents. | ERP, warehouse management, commerce, procurement applications | Martini correlates control numbers and purchase-order numbers, maps segments and qualifiers, checks required fields, and prevents duplicate downstream orders. |
| Invoices | Represent billing transactions sent to a trading partner after fulfillment or shipment. | ERP, accounting applications, customer portals, trading-partner networks | Martini maps invoice lines, taxes, totals, terms, and identifiers, validates business rules, and generates the required outbound EDI or structured payload. |
| Shipments | Represent shipment confirmations and advance shipment notification data exchanged with partners. | Warehouse platforms, ERP, commerce applications, carrier processes | Martini enriches shipment data with warehouse, package, carrier, and tracking information, then produces partner-specific ASN or shipment documents. |
| Products | Represent item, SKU, catalog, pricing, and partner-specific product information. | ERP, commerce platforms, warehouse systems, product catalogs | Martini normalizes SKU and unit-of-measure values, applies partner code conversions, and synchronizes approved product data with target applications. |
Authentication and security considerations
Environment-specific authentication
TrueCommerce authentication depends on the provisioned product and channel. API credentials, secure file-transfer credentials, AS2 certificates, HTTPS, signing, encryption, and receipt acknowledgements may be relevant.
Credential protection
Martini should keep API credentials, SFTP secrets, certificates, and other transport settings in environment configuration rather than workflow mappings or source logic.
Partner and transport controls
- Restrict API endpoints and callback surfaces to the required systems.
- Rotate certificates and credentials according to the TrueCommerce channel requirements.
- Protect original EDI files and transaction data according to enterprise retention and access policies.
Operational considerations for TrueCommerce integrations
Transactions and throughput
Confirm API pagination, rate limits, maximum payload sizes, batch behavior, and retry guidance for the specific TrueCommerce product. File-based workloads require atomic pickup, archive, quarantine, and retention rules.
Idempotency and ordering
Use trading-partner identifiers, control numbers, purchase-order numbers, invoice numbers, shipment identifiers, and provider references to prevent duplicates. Do not assume that related orders, shipments, invoices, and acknowledgements arrive in order.
Validation and change management
Separate transport delivery, technical processing, EDI acknowledgement, and business acceptance statuses. Version partner mappings and document rules independently from workflow orchestration, and test changes against representative X12, EDIFACT, API, and partner-specific payloads.
Replay and monitoring
Retain the original payload or file reference, partner identity, transaction identifiers, validation errors, and downstream responses. Monitor failed workflows, rejected documents, certificate expiry, and reconciliation gaps, with controlled replay for recoverable failures.
Why use Martini instead of scripts or point-to-point integrations?
One orchestration layer for mixed channels
TrueCommerce implementations often combine APIs, EDI files, SFTP, AS2, managed exchange, and partner-specific document rules. Martini provides a consistent workflow model across those channels without requiring every integration to be implemented as an isolated script.
Reusable transformation and routing
Martini can separate shared canonical transformations from partner-specific mappings, validations, code conversions, and routing decisions. This helps teams manage multiple retailers, suppliers, ERPs, commerce platforms, and warehouse systems without duplicating all processing logic.
Operational control
- Track transport, technical, acknowledgement, and business statuses separately.
- Apply idempotency, retries, quarantine, and replay rules in workflows.
- Expose controlled APIs for upstream applications or confirmed callbacks.
- Keep credentials, certificates, and environment-specific configuration outside workflow logic.
Frequently asked questions
TrueCommerce can be integrated through EDI and secure file exchange such as SFTP or AS2, managed transaction services, and REST APIs available in some product offerings. Selected services may also provide callbacks or notifications. The appropriate mechanism depends on the provisioned TrueCommerce product, trading partners, document standards, and channel configuration.
Yes. Martini can integrate with TrueCommerce through confirmed REST APIs, EDI and structured file exchange, SFTP, AS2, managed transaction endpoints, and supported callbacks. Martini workflows can validate, transform, route, and reconcile transactions with ERP, commerce, warehouse, and other enterprise systems.
No. A dedicated TrueCommerce connector is not required. Martini can use TrueCommerce’s confirmed native integration mechanisms, including APIs, EDI file exchange, SFTP, AS2, managed transport services, or supported callbacks, with authentication and certificates configured for the relevant environment.
Lonti does not charge an additional per-connector or per-vendor fee to integrate TrueCommerce. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from TrueCommerce, cloud infrastructure, transport providers, or other third-party systems based on subscription, usage, and deployment model.
Use the TrueCommerce API when the required product endpoint and credentials are provisioned and suitable for the transaction volume. EDI through SFTP, AS2, managed services, or other configured file channels is central to many implementations. Batch processing is common, while GraphQL and a general-purpose SOAP API were not confirmed.
Callback or notification capabilities may be available for selected TrueCommerce products or event types, but universal webhook coverage for every EDI document was not verified. Confirm the required events with TrueCommerce; otherwise use scheduled polling, file pickup, acknowledgements, or status reconciliation.
Martini receives or retrieves API payloads and EDI files, identifies the trading partner and document type, validates the input, and maps it into a canonical or target application model. Partner-specific mappings handle qualifiers, codes, segments, units, and required fields, while outbound workflows generate the required acknowledgements, shipment documents, invoices, or other responses.
Martini can retain original payloads or file references, transaction identifiers, validation results, downstream responses, and processing status. Workflows can detect retransmitted documents using control numbers, purchase-order numbers, invoice numbers, and shipment identifiers, quarantine failures, retry transient errors, and support controlled replay without creating duplicate business records.
Related Martini documentation
Workflows
Transformation
Build a maintainable TrueCommerce integration with Martini
Use Martini to orchestrate TrueCommerce APIs, EDI files, secure transport channels, partner-specific mappings, acknowledgements, and enterprise application workflows in one controlled integration environment.