Skip to main content
Find quick answers to the most common questions about Leara. Each answer is self-contained and links to detailed articles where available.
Leara is unified commerce for modern merchants: orders, inventory, and product data in one operation. Articles come from your business system; variants, images, and groups are added in Leara. The office works in the web interface, the warehouse in the app, checkout stays in the shop, and invoicing remains in the business system.
It means commerce is not split between shop, warehouse, and accounting. Product, stock, and order live in Leara and are shared with the business system, e-commerce, and shipping. A web order, a warehouse pick, or an invoice in the business system updates the operation as it happens, not in an overnight batch.
Point-to-point solves one flow at a time and stops at the weakest register. In Leara, commerce sits in the middle: business systems and e-commerce read and write against orders, inventory, and product data there, so fields do not disappear along the way.
E-commerce, in-store via order and pick, B2B orders, and multiple warehouses. Leara does not have its own cash register. Channels differ in how the order is created, not in how it is picked, invoiced, and stored.
Business systems, e-commerce, and shipping, targeting the systems you already run. Live and planned integrations are shown in Architect. Leara does not promise integrations that are not yet available.
Sync happens continuously on order, inventory change, or invoice event. Exact latency depends on the business system and configuration, but the principle is that data does not wait for overnight batches.
Yes. Web orders and orders you create land in the same order book. Channel and location follow the order, and status runs from created to picked.
Stock levels update event by event: order, pick, receipt, adjustment. Not in batch. What you see in Leara is current for the next order.
Yes. Multi-warehouse and store stock can be modeled with separate balances and visibility per channel. You control which warehouses are allowed to sell what, and reservations stay consistent across the network.
Product data lives in Leara: articles, variants, groups, attributes, brands, suppliers, images, and price files. What the business system lacks, the e-commerce is fed with.
No. You can phase in channel by channel, for example e-commerce first, then warehouse and store, without double-maintaining core data.
Use the support form at /support or email support@leara.se. Describe the issue with steps, error messages, or order numbers, and the team will reply to the address you provide.