Warehouse ERP and storewithout an integrator.

The usual setup: a store from one company, a warehouse program from another, and a third company that connects them for its own subscription. Every change on either side means a call to the middleman. This text shows a connection that is part of the store, not a separate product.

What flows and in which direction

From the program to sales: product codes from the product file (the catalogue number stays the product's identity), barcodes, stock from chosen warehouses and prices. There are often two price levels: retail for the store and wholesale for the B2B portal. Build the category tree for buyers separately, because warehouse groups serve the warehouse, not the customer.

The other way goes the order, saved in the program as a customer order, plus new customers. One system issues the invoice: your program or the store. Never both, because two documents with different numbers for one sale are an accounting problem.

How often data moves

Warehouse programs usually do not announce changes, so the store asks them regularly. Stock should refresh often, the full catalogue less often. What matters more than the rhythm is what happens when something fails: an order that did not save in the program must be visible in the panel, not lost in a log.

What it takes to launch

• Secure access to your program's database or interface, on an account with limited permissions.
• A person who knows your setup: warehouses, price levels, document series.
• A decision on who issues the invoice: the program or the store.
• A product sample and a test order that go the full way before launch.

Torveo connects with WAPRO Mag, Subiekt nexo, Streamsoft Prestiż, Symfonia, enova365 and Comarch ERP Optima. We launch the connection in the Business package after reviewing your installation, then look after it under ERP care.

Sales connected to the warehouse means one source of truth for product, price and stock. Everything else is retyping.