Logo GO 3 Integration

What exactly gets written into GO 3?

Once connected, these record types can be transferred: contacts, sales invoices, expense invoices, product cards, stock movements, sales prices, sales orders and dispatch notes. All of them are written into GO's own resources; Stokzone puts no intermediate table in between, so what you see in GO is your actual record.

The expense-invoice item is particularly useful and the one most often missed. Marketplaces deduct commission, shipping and fees from your settlement, and those amounts have to appear as expenses in the books. Tracked by hand they usually never get entered, and profit ends the month looking higher than it is.

Which components have to line up during setup?

The GO 3 connection runs through Logo Objects, and the REST interface sits on top of that component. So two things have to be right together: Logo Objects must be running, and its version must line up with your ERP engine's.

The symptom of a version mismatch is recognisable: the connection test appears to pass, yet operations fail inconsistently. If things got strange right after an upgrade, this is almost always why — upgrading both components together removes the problem before it starts.

You also do not pay Logo separately for the REST interface; it is not licensed as its own product. Your existing Logo Objects licence covers it.

How do the product and stock sides work?

Alongside the document side there is a product side. Product cards in GO can be listed, read one by one and updated from Stokzone. That means not having to edit the same product in two places — when a name, code or price changes you work from one place.

Stock movements and sales prices are written separately too. That separation matters: you do not have to touch a stock record to update a price, or push a price to correct stock. You send only what changed, without creating movements nobody asked for in the books.