Optima as the back office for B2B sales
Comarch ERP Optima is a business management system aimed at small and mid-sized companies and accounting offices, available both on-premises and in the cloud. For a distributor or a manufacturer, the part that matters here is Trade and Warehouse: that is where product records, product groups, defined sales prices, warehouses, customers with their commercial terms and documents live.
The integration has one goal: sales reps and accountants keep working in Optima, and nobody retypes the same data into the shop or back again.
What flows between the systems
| Data | In Optima | In Endora Commerce | Typical direction |
|---|---|---|---|
| Product records | product cards: names, codes, attributes, product groups | product catalog and categories | agreed field by field |
| Stock levels | stock held in warehouses | availability on the storefront | from Optima to platform |
| Prices | sales prices and individual customer terms | price lists and contracts in the pricing engine | from Optima to platform |
| Sales documents | trade documents | orders placed by customers | from platform to Optima |
Stock is kept current so the storefront does not show an item that Optima has marked as unavailable. Prices go into the pricing engine, not into a static table: a logged-in customer sees their own price, resolved on the platform side, so catalog speed does not depend on how busy the ERP database is at that moment.
The adapter uses the platform’s partner API and signed webhooks. Events such as an order being created or its status changing are sent with an HMAC-SHA-256 signature and retried on failure, so a short outage on the ERP side does not mean a lost order.
Decisions to make before go-live
Optima is a broad system and every company uses it a little differently. That is why the scope and direction of each flow (what moves from Optima to the platform, what moves back, and how often) is agreed during the discovery workshop, before the adapter is configured for a specific rollout. The questions that come up every time:
- Which document an order should come back as. In Optima, the natural counterpart of a customer order is the Customer Reservation (Rezerwacja Odbiorcy, RO), which reserves the goods and which a sales rep later converts into a sales invoice. Whether that is the right choice for you is part of agreeing the document format.
- Which Optima prices are B2B price lists. Optima lets you define your own sales prices, assign a default price to a customer and apply discounts. You need to decide which of them become price lists for customer groups and which become contract terms for a specific company.
- Which warehouses count towards availability. Not every warehouse in Optima should be visible to online sales.
- Who owns the product description. Codes, names and groups usually come from the ERP, but marketing copy and images are often created in the platform or in a PIM. An ERP connector and a PIM connector can run side by side.
- Who issues the invoice. If all sales go through Optima, the ERP can handle the invoice and its submission to KSeF. If invoices are to be issued in the platform, that is the job of the separate KSeF integration.
What to prepare on the Optima side
- Clean product records: unique product codes, consistent product groups and attributes, because these become the structure of the catalog.
- Customers with correct tax IDs (NIP) and assigned commercial terms, if prices are to be individual.
- Which variant you run: on-premises, the Optima database runs on Microsoft SQL Server in your own infrastructure; in the cloud model, it runs at Comarch. This determines how the adapter gets access to the data, so we settle it at the very start, together with whoever looks after your installation.
- An operator and permissions in Optima dedicated to the integration, so that automatically created documents can be told apart from manually entered ones.
Current requirements and a description of the modules are on the Comarch ERP Optima product page.
The Optima adapter landed in one of the platform updates, together with the Subiekt GT and KSeF integrations.