What API2Cart Is Evaluating for metasfresh Integration
Candidate workflow
Align online demand with business partners, products, orders, inventory, and shipments. Final entity and method coverage will follow verified vendor interfaces and customer requirements.
Operational outcome
The intended result is to retain organization, warehouse, attribute, unit, pricing, tax, and fulfillment context. Identity rules and idempotency would be defined before transactional writes are enabled.
ERP safeguards
The design must support self-hosted customization without assuming identical schemas across installations. Customers, products, sales orders, fulfillments, invoices, and production records would keep their distinct lifecycle roles.
Develop Integrations Faster and Save Up to 9x on Costs
Trusted by
What We Know About metasfresh So Far
Based on metasfresh’s own documentation and API2Cart’s discovery process — not a promise of a release date.
API & Integration. metasfresh provides a REST/JSON API, documented and browsable through a built-in Swagger UI (a frontend instance at /swagger-ui.html and a backend instance at /app/swagger-ui.html). Authentication uses a bearer-style auth token generated from the user's profile and passed with each request rather than an OAuth flow. The API supports composite requests that create several related records (e.g., a business partner and a product) in one call, useful for migration-style imports; published rate limits and a formal versioning scheme are not documented.
metasfresh integration is not live yet. Authentication, modules, entities, fields, writes, events, limits, editions, and release timing remain subject to technical discovery and demand.
Background. metasfresh is an open-source ERP platform with a Java and PostgreSQL back end and a web interface. Its architecture separates the application, Web API, database, reporting, search, and optional material-scheduling services, making deployment topology relevant to integration planning.
Where it specializes. The platform emphasizes sales, procurement, warehouse and materials management, handling units, manufacturing, products, business partners, invoicing, and accounting. It is especially relevant to product and supply-chain organizations that need detailed packaging, warehouse, availability, material-planning, and order-disposition workflows.
Integration challenge. metasfresh documents a JSON REST web service with Swagger and authorization tokens stored against users. Published endpoints cover order candidates and orders, partners and contacts, products and categories, invoices, files, and data import. The API supports external IDs and explicit synchronization advice such as create, merge, ignore, or fail, and can create related records within one migration request. API2Cart must preserve tenant, organization, warehouse, handling-unit, product, tax, and document context; define stable external IDs; select safe sync advice; and verify which endpoints exist in the installed release and custom modules.
Technical validation. Engineering must validate REST services, authentication, version, tenant isolation, and customizations. Unsupported modules and operations would remain outside the public scope.
Roadmap evaluation considers API maturity, sandbox access, operational correctness, commerce relevance, scale, customer demand, maintenance cost, deployment variants, and overlap with existing connectors. This page records a candidate, not a promised release date.
Primary sources: metasfresh REST API guides · metasfresh REST synchronization model · metasfresh system architecture
Related planned integrations: Tryton integration · ADempiere integration · Oracle Fusion Cloud ERP integration · Microsoft Dynamics 365 Business Central integration
Interested in metasfresh Integration?
Let us know you’re interested, and we’ll notify you as soon as metasfresh support becomes available.
