Built to coexist with your ERP.
Built to talk to your WMS.
Your ERP keeps the books and the customer orders. Your WMS keeps the warehouse picks. Ignite Lean is everything between them — the production execution layer that runs the floor and pushes status back to both.
- Production orders
- Visual work instructions
- Kiosk-driven build execution
- Kit-level traceability
- Quality (CAPA · NCs · audits)
- Maintenance (assets · WOs · PM)
- Operator guidance & training
- Production KPIs & analytics
What lives where.
The cleanest architecture is the one where each system owns what it's best at. Here's the honest split.
Your ERP keeps
- Customer master + accounts
- Sales orders + invoices
- Purchasing + AP / AR
- General ledger + financials
- Period close + reporting
- Statutory + tax compliance
Ignite Lean owns
- Production orders + scheduling
- Work instructions + canvas
- Kiosk-driven build execution
- Operator training matrix
- Quality NCs + CAPA + audits
- Maintenance work orders + PMs
- Kit-level traceability + build records
- Production KPIs (throughput, MTBF, OEE)
Your WMS keeps
- Warehouse inventory by location
- Pick + put-away rules
- Replenishment triggers
- Receiving + shipping
- Lot + serial reservations
- Carrier integrations
Kiosk picks. Andon parts calls.
The operator at the workstation needs a part. Today: walks to the bench, hunts down a supervisor, the supervisor walks to the warehouse window, the warehouse looks it up, somebody radios back. Five minutes of standing still per call, repeated all shift.
With Ignite Lean's WMS integration, the operator taps "Call for parts" on the kiosk. The pick request is in the WMS queue before the supervisor has been paged. If the part is short, the andon-style alert hits the supervisor's phone with the workstation + the missing SKU pre-filled. They radio the warehouse with concrete info, not "uh, station 4 needs something."
Same model for replenishment: kit-level consumption from the kiosk events flows to the WMS so reorder points fire on actual production usage, not estimates.
Available today vs roadmap.
Honest framing. We don't claim turnkey connectors that don't exist yet — those land when paying customers ask by name.
- REST APISupabase-powered, JWT-authenticated. Read + write on every domain entity (production orders, builds, NCs, work orders, assets, parts).
- Excel / CSV import + exportBulk-import production orders from Excel; export build history, NCs, and work orders to CSV.
- Outbound webhooks (custom payload)Via Edge Functions — fire your own URL on any event (build complete, NC opened, WO closed).
- Personal Access TokensLong-lived bearer tokens for service-to-service API access. Format
il_pat_xxx…; managed under Settings → Integrations with one-shot reveal and per-token revoke. - Public API documentationOpenAPI 3 spec rendered with Redoc at /api-docs. Endpoint examples, PAT auth flow, schema reference.
- Zapier & Make.com (no-code)Use the outbound webhooks as Zap / Make triggers, and a Personal Access Token for the read side ("Custom GET"). No proprietary connector required — it's just bearer auth + JSON. Recipes in the API docs.
- Native ERP connector (pilot)Platform scaffold in place — provider adapter ships with the first paying pilot. Targets: QuickBooks, NetSuite, SAP, Sage, Odoo, Dynamics, or any custom REST API. Per-org config + secret vault + sync audit log already live on the platform side.
- SFTP file drops (on request)Common pattern for legacy ERPs. Nightly batch drop of completed-orders CSV — we wire it up per customer.
- Native SAP Business One connectorBidirectional: SAP B1 sales orders → IL production orders; IL completed builds → SAP B1 production receipts.
- Native Microsoft Dynamics GP connectorSame bidirectional sync for GP's manufacturing module.
- Native Oracle / JD Edwards connectorAligned with the SMB mid-market footprint for JDE EnterpriseOne.
- Native WMS connector (Fishbowl first)For the kiosk-pick + andon parts-call flow above.
- Zapier + Make.com appsFor everyone outside the named-connector list who wants no-code workflow automation.
ERPs we play well with.
Honest scope per ERP. Native connectors land when paying customers ask by name. Until then: REST API + Excel / CSV + webhooks get you the same outcome with more glue code.
SAP Business One
Common in 50–500 employee manufacturers. Native B1 connector on the Q1–Q2 2027 roadmap. Today: REST API + CSV import of SAP B1 production-order export gets you 80% of the value.
Microsoft Dynamics GP
Long-standing SMB favourite, especially in North America. Native GP connector on the same Q1–Q2 2027 roadmap. Today: same REST / CSV pattern.
Oracle / JD Edwards
JDE EnterpriseOne and Oracle Cloud ERP both well-suited to Ignite Lean as the floor-execution layer. Bidirectional connector roadmap.
Epicor
Epicor Kinetic and ERP. Strong manufacturing fit. Same REST + CSV pattern today; named connector roadmap.
NetSuite
Most common SMB cloud ERP. NetSuite's native REST API plays well with our REST API for a custom-built integration today.
Infor / Sage
Common in distribution-heavy manufacturers. Same connector roadmap. Today's REST + CSV pattern works.
Want to pilot a custom connector?
We build the first native connector to whatever ERP / WMS your shop is on, in exchange for being your pilot reference customer. Three slots available in 2027.