Connect Logo to your store around your business rules
Re-entering orders, editing prices twice and finding missing transfers takes time. We assess the rules a ready-made connector cannot cover against your existing Logo product and storefront.
Tell us about your Logo integrationA written scope and a fixed budget before any work is billed.
Start with the product, version and access
The Logo name does not identify a single integration method. According to Logo’s own documentation, the Logo REST Service runs only on the 3-series products: Tiger 3, Tiger Enterprise 3 and Tiger Wings are listed as compatible; Go Plus, Go 3, Logo Start, Tiger Plus and Tiger Enterprise as incompatible. The service has no licence of its own. It runs on Logo Objects, so a Logo Objects licence must be present.
For a product without the REST service, which connection route is available is assessed in discovery from the tools that product exposes. The company and accounting-period setup, firewall and proxy port permissions, and the certificates HTTPS needs are part of the same review. Additional licences or access requirements are separate from development scope.
This is a custom development service, not a packaged connector or a claim of Logo partnership. We do not promise compatibility with every version or a delivery date before checking feasibility.
- The exact Logo product and version
- Store platform and available API documentation
- Source systems for orders, customers, inventory and prices
- Test environment, permissions and responsible teams
Map orders and customer accounts
Agree how a store customer maps to an ERP account. New customers, guest checkout, tax details and duplicate records need separate rules.
Keep the store order identifier throughout the transfer. Define which system owns cancellations, returns and partial fulfilment; invoice creation is assessed separately.
Give inventory and prices a clear owner
Choose one source of truth for each field. Agree warehouse, available quantity, price-list and currency mappings before enabling updates in both directions.
Update frequency depends on API limits and operational needs. Concurrent sales and connection failures remain risks that the design must address.
Make failed transfers visible
A disconnected system needs a retry path without losing records or creating a second order. Define the exception queue, alerts and responsibility for manual corrections.
Reconcile store and ERP records at agreed intervals. Missing or different records should be traceable to the relevant order.
A ready-made product or custom development?
If an existing product covers standard order, inventory and invoice flows, assess it first. Custom pricing, an unusual storefront or approvals across internal systems may justify development.
Cost depends on connections, fields, data cleanup, failure cases and support. Vendor licences and third-party fees are itemised separately.
Before starting an integration
The ones that come up most in first conversations about this service.
Something not covered here?
Email us at hello@kodfabrika.com.
Built to last.
Started this week.
Tell us what you’re building. You’ll receive a written scope, a defined budget, and a delivery plan. Not a proposal deck.