Retail and eCommerce / Nimex Solutions
Your web shop and your stores, selling from one stock.
Odoo eCommerce and Point of Sale share one catalogue, one set of prices and one inventory. Nimex adds what Turkish retail needs around them: a checkout that never fails at the last click, iyzico card payments, e-Arşiv invoices and cargo labels.
- Standard Odoo
- Built by Nimex
- What we build
Web order S00412Paid
2,400TRY · iyzico 3-D Secure
Ceramic mug set · one stock
Shop page 12Store till 12
INV/2026/00731 · e-Arşiv
Successful PDF archived
Retail challenges
Two counters, one customer. The systems behind them must agree.
Shoppers move between your web shop, your stores and the marketplaces. Each place sells the same products, so stock, prices, payments and invoices must come from the same records, and fail early rather than at the till or the payment page.
-
The web shop sells what the store just sold
Separate stock lists mean the last unit is sold twice, and someone calls the customer to cancel.
Standard OdooOne inventory behind eCommerce and Point of Sale: a web order reserves the unit the till can no longer sell.
-
Card payments fail at the last click
Turkish gateways refuse to start a payment when the buyer address is incomplete, and the shopper sees a confusing error.
Built by NimexA checkout address guard keeps the shopper on the address form until the data the gateway needs is complete.
-
Every sale needs the right official document
Consumers and non-registered buyers get e-Arşiv, registered businesses get e-Fatura, and returns need their own type.
Built by Nimexe-Arşiv and e-Fatura through Nilvera, routed per contact from the provider's registry, official PDF kept on the invoice.
-
Marketplaces and carriers live outside the ERP
Orders are retyped from marketplace panels and tracking numbers copied from carrier websites.
Standard OdooAmazon and Shopee connectors. Yurtiçi Kargo and Aras Kargo connectors are built by Nimex, scope confirmed per project; Turkish marketplaces after a technical review.
Workflow demonstration
A web order from checkout to e-Arşiv, on one stock.
The shopper cannot reach the payment step with an incomplete address. iyzico's hosted 3-D Secure page takes the card, Odoo verifies the payment server-side before the order is confirmed, the delivery reserves the units both channels see, and the e-Arşiv invoice goes out through Nilvera.
- Address guardNo payment step until the billing address holds the data the gateway requires.Built by Nimex
- iyzico 3-D SecureHosted checkout; the order is confirmed only after server-side verification.Standard Odoo · deployed by Nimex
- One stockThe delivery reserves the units; the shop page and the till show the same availability.Standard Odoo
- e-Arşiv through NilveraSent and waiting response, then Successful; the official PDF is kept on the invoice.Built by Nimex
Retail capabilities
What Odoo does, what we have built, and what we build for you.
Every capability carries its label. Standard Odoo is configured and delivered by our team; Built by Nimex exists in our code and has run for clients; What we build is a capability we offer, shown here as a scope, not as a delivered product.
Selling in stores and online
- Standard Odoo
Point of Sale for every till
Sessions, cash and card in one order, loyalty programmes, receipts and offline selling on tablets and touch screens.
Odoo Point of Sale - Standard Odoo
eCommerce on the same catalogue
Variants, price lists, promotions, customer accounts and checkout, published from the products the stores sell.
Odoo eCommerce - Standard Odoo
One inventory, every channel
Reservations, transfers between stores and the warehouse, replenishment rules and barcode operations.
Odoo Inventory
Built by Nimex for Turkish shops
- Built by Nimex
Gateway-safe checkout address guard
An incomplete billing address, or delivery address for physical goods, sends the shopper back to the form with a warning. The checkout itself is untouched.
In the solutions directory - Standard Odoo · deployed by Nimex
iyzico card payments
Odoo 19's standard iyzico provider, configured and tested for shop checkout and portal invoice payments, verified server-side before an order is marked paid.
Payment integrations - Built by Nimex
e-Arşiv and e-Fatura through Nilvera
Routing per contact from the provider's registry, templates, preview without issuing, return invoices with the right type, official PDFs kept on the invoice.
The e-invoice suite - Built by Nimex
Yurtiçi Kargo and Aras Kargo labels
Shipments created from validated deliveries, carrier labels returned to Odoo, tracking statuses written back. Feature set and carrier service confirmed per project.
Cargo connectors - Built by Nimex
Storefront header and snippets
Branded desktop and mobile headers, product sliders, tabbed category showcases and course or bundle storefront blocks, all editable in the website builder.
Portals and web - Built by Nimex
Datasheets and KVKK sign-up
Up to four PDF datasheets per product page, and a sign-up form that refuses to create an account until the visitor accepts the KVKK notice, enforced on the server.
See both in the directory
What we build for your project
- Prototype · what we build
EFT-POS terminal bridge
A provider-agnostic pattern that sends the amount from the till to a payment terminal through a token-secured service. A prototype: each terminal model needs its own driver, and refunds and settlement are not part of it.
- What we build
Turkish marketplace connectors
Trendyol, Hepsiburada and n11 orders and stock, engineered after a technical review of the marketplace's access for your account.
Marketplace integrations - What we build
Omnichannel day dashboard
Sales per channel and store, top products and open e-Arşiv responses on one screen, defined once on standard Odoo data.
Reports and dashboards
In the interface
Screens your shop team and your customers will use.
Product page with downloadable datasheets
Up to four PDF files per product, validated on upload, with the variant selector under the product name. Stock and price come from the same Odoo records the stores use.
KVKK consent at sign-up
Surname and mobile required; no account without consent, checked on the server.
EFT-POS terminal bridge
The till waits while the amount goes to the terminal; a decline allows a retry. Each terminal model needs its own driver.
Cargo label and tracking on the delivery
The shipment is created at the carrier from the validated delivery; the label comes back to Odoo and a scheduled job writes the carrier's statuses. Scope, carrier service and Odoo version are confirmed for each project.
Retail dashboard
The day across channels, from the same orders.
Web orders count once paid and confirmed; till sales once the session posts. Channel figures add up to the day's total, and every line drills down to the order behind it.
Composition on sample data. Channel figures: 18,400 + 11,280 + 8,940 = 38,620.
See the sales dashboardRelevant integrations
Payments, documents, carriers and marketplaces.
Each tile says where the integration stands: built by Nimex, a standard Odoo connector we deploy, or one we engineer after a technical review.
- iyzico Standard · deployed by Nimex
Hosted 3-D Secure checkout for the shop and portal invoices.
Payments - Nilvera · GİB Built by Nimex
e-Arşiv and e-Fatura, return invoices and official PDFs.
Financial documents - Yurtiçi Kargo · Aras Kargo Built · per project
Shipments, labels and tracking from deliveries, scope confirmed per project.
Cargo - Amazon · Shopee Standard Odoo
Odoo's own marketplace connectors for orders and stock.
Marketplaces - Trendyol · Hepsiburada · n11 After technical review
Engineered once the marketplace's access for your account is reviewed.
Marketplaces - EFT-POS terminals Prototype
Bridge pattern from the till to a terminal; a driver per device model.
Payments
Nimex engineering for retail
The small pieces that keep a Turkish shop running.
We extend standard Odoo where it stops short: at the payment gateway, at the tax authority, at the carrier and on the storefront. Every extension is upgrade-safe and leaves the standard flow in place.
- Checkout and paymentsAddress guard, iyzico deployment, course and bundle checkout for eLearning shops.
- Official documentse-Arşiv, e-Fatura and return invoices through Nilvera, with previews and archived PDFs.
- StorefrontBuilder-native headers and snippets, product datasheets, KVKK-compliant sign-up.
Related Custom Engineering
- Finance · localisationTurkish e-invoice suite
e-Fatura, e-Arşiv, returns and incoming invoices through Nilvera.
Explore the e-invoice suite - IntegrationsCargo and logistics integrations
Yurtiçi Kargo and Aras Kargo from the delivery order, confirmed per project.
Explore the cargo connectors - Portals and webStorefronts and portals
Builder-native storefront blocks, datasheets, KVKK sign-up and checkout guard.
See portals and web - DirectoryEvery retail and e-commerce solution
The full list, filtered to retail and e-commerce, with the evidence for each.
Open the filtered directory
Qualified. Cargo connectors: feature set, carrier service and Odoo version confirmed per project. EFT-POS bridge: a prototype pattern, not a certified terminal integration. Turkish marketplaces: engineered after a technical review.