Logo GO 3

Logo's entry ERP tier for small KOBİs — commercially enormous installed base, functionally lean. For agent builders GO 3 is both the biggest audience and the most constrained surface.

Why agents care

• Read access: with a database usage license, direct read access to the GO 3 database is a sanctioned pattern (as with Start 3) — enough to ground an agent in orders, stock, and customer balances.
• The planning gap is the opportunity: GO 3 has no MRP. Requirement calculations (recipe × open orders vs. stock) happen in Excel at most small manufacturers. An agent that projects raw-material needs and flags days-of-stock from GO 3 reads replaces the most error-prone spreadsheet in the company.
• Writes still belong on the Objects/REST path where available — see Integration Surfaces — How Agents Read and Write Logo.

Boundaries

No planning module means no planning data — an agent building requirement projections is computing new state, not reading it, and should present results as drafts for human confirmation.

Related: Logo Tiger 3 (the tier above, with MRP in Enterprise).