DiCentral is a US-origin EDI (Electronic Data Interchange) and supply-chain-integration service provider, headquartered in Houston, Texas, with European operations including a DACH presence. The product is positioned as a cloud-based EDI managed-service rather than an on-premises EDI software package, with the business model being subscription-based managed integration rather than perpetual-licence software. DiCentral targets retailers, manufacturers, distributors and 3PLs that need to exchange standardised supply-chain documents (orders, shipping notices, invoices, inventory advices) with trading partners over EDI standards (EDIFACT in Europe, ANSI X.12 in the US, VDA for the German automotive industry, GS1 standards across grocery and consumer goods). The DACH presence covers the German retail, automotive and consumer-goods supply-chain integration patterns.
Architecture and deployment
DiCentral is delivered as a cloud-based EDI service rather than installed software. The architecture is the typical EDI service-provider stack: a cloud platform that handles the protocol layer (AS2, sFTP, OFTP2, VAN-style interconnection), the EDI translation layer (mapping between trading-partner EDI formats and customer-internal data formats), the message-routing engine and a web-based management interface for monitoring, alerts and exception handling. Customers connect their ERP, WMS or other operational systems to the DiCentral platform through standard integration patterns (REST APIs, file transfer, dedicated connectors for common ERPs) and DiCentral handles the EDI-side communication with trading partners. The managed-service positioning means DiCentral typically also provides ongoing partner-onboarding, mapping maintenance and support services.
Functional scope
EDI functional scope covers the standard supply-chain document types: purchase orders (PO, EDIFACT ORDERS, X.12 850), order confirmations (POA, ORDRSP, 855), advance shipping notices (ASN, DESADV, 856), invoices (INVOIC, 810), inventory advice (INVRPT, 846), remittance advice (REMADV, 820) and the various industry-specific extensions for grocery, retail, automotive and consumer goods. Beyond the document layer, DiCentral covers partner-onboarding services (the operationally heavy work of connecting and mapping each trading partner), EDI-compliance handling for retailer-specific requirements (Walmart, Amazon, Carrefour, Metro and many others), GS1 / GDSN data-synchronisation services for consumer-goods customers, and supply-chain visibility dashboards. ERP integration is supported through pre-built connectors for the major mid-market and enterprise ERPs.
DACH positioning
DACH EDI coverage includes the standard German and European retail-grocery EDI patterns (EDIFACT, GS1-EANCOM), the German automotive industry VDA standards (which are different from general EDIFACT and have specific German-OEM idiosyncrasies for BMW, Daimler, Volkswagen, ZF and others), the public-sector XRechnung e-invoicing format and the European-wide Peppol network. DACH-typical trading-partner relationships (German grocery retailers REWE, Edeka, Lidl, Aldi, drugstore-DM, electronics-MediaMarkt-Saturn, automotive OEMs and Tier-1 suppliers) are routinely covered by DiCentral. The competitive set in DACH EDI services includes SEEBURGER, GXS / OpenText, Comarch EDI, Lobster, Crossgate and various regional specialists. DiCentral's US origin gives it strength in customers with North-American supply chains; the DACH coverage is functional but less native-deep than dedicated DACH EDI specialists.
Pricing model and TCO
DiCentral uses subscription pricing with tiers based on transaction volume, number of trading partners and document types. The pricing model is transparent for the standard tiers but materially negotiated for enterprise customers with high transaction volumes. Indicative TCO for a DACH mid-market manufacturer with 30 to 50 trading partners and typical transaction volumes lands in the mid-five-figure range annually all-in, including partner-onboarding services and ongoing operational support. The economic case versus building or running on-premises EDI software is that the managed-service approach offloads the operationally heavy partner-onboarding, mapping-maintenance and protocol-engineering work to the service provider, which is typically cheaper than maintaining the in-house expertise.
Selection considerations
DiCentral is a credible choice for DACH manufacturers, distributors and retailers with North-American trading-partner reach or global supply-chain needs, where the US-origin platform has a natural strength. For DACH-only EDI use cases concentrated in German retail-grocery and German-automotive supply chains, DACH-native EDI specialists (SEEBURGER, Lobster, Crossgate) may provide deeper local relationships and DACH-specific partner-onboarding experience. The selection between DiCentral and the DACH-native specialists often comes down to the geography of the trading-partner network, the breadth of supplier-side or customer-side EDI relationships and the local-language operational support requirements.
Share your experience with DiCentral. We publish reviews after a brief editorial check in 1–3 business days. Fields marked with * are required.
Häufig gestellte Fragen
Which modules does DiCentral offer?
DiCentral typically includes modules for financial accounting, order management, warehousing, purchasing and master data. Industry-specific extensions (PPS, CRM, DMS) are often optional – the vendor profile above shows the exact range of functions. The precise configuration depends on the industry, company size class and customising depth of the specific ERP setup.
What are the hardware requirements for DiCentral?
For cloud deployment, modern browsers are sufficient. For on-premise installations, server requirements vary depending on the number of users and document volume – the vendor provides detailed system requirements, often with recommended configurations for 25, 50, 100 or 250 users. The precise configuration depends on the industry, company size class and customising depth of the specific ERP setup.
How does data migration from a legacy ERP to DiCentral work?
Data migration typically runs in 3 phases: mapping (old vs new data model), cleansing (duplicates, master data quality), and a test migration with validation. Specialised migration service providers: ERP integration providers. The precise configuration depends on the industry, company size class and customising depth of the specific ERP setup.
How expensive is annual maintenance for DiCentral?
On-premise maintenance typically runs at 18–22% of the licence costs per year and covers updates, hotfixes and phone support. Cloud ERPs include maintenance in the subscription price, so there is no separate maintenance contract. Over a typical system lifetime this recurring cost adds up to a significant share of the total cost of ownership, so budget for it from year one.
Which well-known reference customers does DiCentral have?
Vendors usually list reference customers on their own website – for specialised industry ERPs, 10–50 showcase customers are well known. Industry-specific references should be requested specifically before making a selection. The precise configuration depends on the industry, company size class and customising depth of the specific ERP setup.