Truly headless
The core exposes a versioned, documented API. The storefront and the Control Center are clients of that API, not part of the core: launching a new storefront never means touching the business logic.
Headless enterprise commerce
Your ERP leads. Your store sells.
FINORA Commerce turns your ERP catalog, prices and inventory into a fast, secure shopping experience, with payment, stock reservation and reconciliation closed end to end.
- The ERP is the source of truth
- Atomic stock reservation
- Idempotent checkout
- No card data on the platform
- Multi-store and multi-brand
- Standalone Control Center
The platform
Three design decisions that change everything
An enterprise online store is not a pretty page over a copied catalog. It is a disciplined extension of your operation.
The ERP stays the truth
Catalog, prices, stock and parties are read from the ERP. Commerce projects them to search and sell fast, but it never invents prices or rewrites master data.
Operating is not selling
Shoppers and administrators use different applications, identities and permissions. Administrators sign in with a mandatory second factor.
Capabilities
Everything a serious operation needs to sell online
Eight capabilities that work together and are enabled per store.
Massive catalog
Hierarchical categories, brands, variants and configurable attributes, built for catalogs of millions of SKUs. ERP data is read-only and commercial enrichment survives every synchronization.
Forgiving search
Tolerates typos, suggests from the second character and keeps facets in the URL. If the search engine goes down, SKU and name lookups keep answering in degraded mode.
Prices and promotions
Price lists with validity, promotions and coupons. The price a shopper sees is computed by the server, never by the browser.
Multi-warehouse inventory
Availability per warehouse and atomic reservation: two shoppers cannot end up with the same last unit.
Idempotent checkout
Retrying a payment or reloading the page never duplicates orders or charges. Every critical operation carries an idempotency key.
Control Center
A standalone application for catalog, orders, promotions, returns and store settings, with role-based permissions and auditing.
Multi-store, multi-brand
One installation, several stores isolated from each other, each with its own theme, currency, catalog and rules. Isolation reaches the database.
Optional AI
Semantic search and content assistance as add-ons. Switch them off and the store works the same: no module depends on AI.
ERP integration
Connected to your ERP, not stacked on top of it
Each ERP plugs in through a connector that implements a common port. iDempiere is officially supported; other ERPs integrate by writing an adapter against the same contract, without changing the core.
Official support
iDempiere
Other ERPs
via adapter
Reads from the ERP
- Categories and catalog
- Prices and price lists
- Stock per warehouse
- Parties and customers
Writes to the ERP
- Orders with their own reference, idempotent
- In the demonstration they arrive as drafts: inventory and accounting stay untouched
Money rules, spelled out
- Price source
- ERP, always
- Store currency
- USD
- Rounding
- 2 decimals per line, half up
- Reconciliation
- Gross total, taxes included
Payments
Get paid with FINORA Merchant or the processor you choose
Payments live behind a port. The primary provider is the hosted checkout of FINORA Merchant; other authorized processors plug in as adapters. Shoppers pay on the provider page: card data never goes through Commerce.
- Hosted checkoutSensitive data capture happens outside the platform, in the provider environment.
- Signed notificationsEvery payment notice is signature-verified before it touches an order.
- Partial refundsAsynchronous refunds reconciled against the provider, with an audit trail.
- Labeled test modeA simulation provider clearly marked SANDBOX on screen and on receipts.
- Shopper
- Provider checkout
- Signed notice
- Order paid
Commerce only receives the outcome, never the card number.
Security
Security by design, not as a patch
Verifiable controls at every layer, with the attack surface cut down to the essentials.
Standard identity
OIDC with PKCE, one client per application and a dedicated audience for the API.
MFA for administrators
The Control Center requires a TOTP second factor. The storefront shares no session with it.
PCI out of scope
No card numbers on the platform: scope stays with the payment provider.
Per-store isolation
Row-level security in the database: one store cannot read another store data.
Auditing
Sensitive administrative actions are recorded with author and timestamp.
Hardened browser
Content security policy with nonces, sealed cookies and zero third-party scripts.
Architecture
A clean core with swappable adapters
Business modules never know the ERP, the payment provider or the search engine: they talk to ports. Swapping an adapter does not change the business.
Channels
- Online store
- Control Center
- External systems via API
Business core
- Catalog
- Search
- Pricing and promotions
- Inventory
- Cart and orders
- Payments
- Fulfillment
- Audit
Ports and adapters
- ERP (iDempiere and others)
- Payments (Merchant and others)
- OIDC identity
- Search engine
- Database and cache
- Events and notifications
Arrows always point toward the core: adapters depend on the business, never the other way around.
The demo walkthrough
A complete sale, round trip to the ERP
Seven steps the demonstration walks end to end, from master data to reconciliation.
-
Step 1: ERP
Catalog, prices and stock are read from the ERP and published to the store.
-
Step 2: Search
The shopper finds the product, even with typos, and narrows it down with facets.
-
Step 3: Cart
The server recalculates prices and promotions on every change. The browser never decides a price.
-
Step 4: Payment
The shopper pays on the provider hosted checkout. Commerce receives only the signed outcome.
-
Step 5: Reservation
With payment confirmed, stock is reserved atomically in the right warehouse.
-
Step 6: Order in ERP
The order travels to the ERP with its reference, exactly once. In the demonstration it stays as a draft.
-
Step 7: Reconciliation
Order, payment and ERP document are matched on the gross total and any difference is flagged.
Sectors
For those who really sell, to many, at volume
Any business with an ERP and a catalog that deserves its own storefront.
Retail
Fashion, home and electronics with variants and seasons.
Supermarkets
Wide assortments, shifting prices and per-branch stock.
Pharmacies
Extensive catalogs with attributes and per-location availability.
Hardware stores
Thousands of technical items searched by size, brand or code.
Distributors
Recurring orders, per-customer price lists and replenishment.
Manufacturers
Direct and channel sales from the same master catalog.
B2B wholesalers
Company accounts, commercial terms and volume purchasing.
Try it
Walk the complete sale in the demonstration
Open the demo store, buy a product and follow the order all the way to the ERP. If you prefer a conversation, write to us.