Where ERP ends and engineer-to-order coordination begins.
An elevator manufacturing ERP system manages accounting, inventory, purchasing, production, and financial control. But a custom elevator cab is engineer-to-order work: its specification can keep moving through survey and engineering. Many cab shops therefore keep ERP for transactions while coordinating the actual job through email, spreadsheets, drawings, and meetings.
Published
Enterprise resource planning creates one transactional system for money, material, labour, and production. A real manufacturing ERP is strongest when stable part numbers, repeatable bills of materials, routings, inventory movements, and accounting entries describe the operation. Its modules are connected so a sales order can create demand, purchasing can satisfy it, production can consume material, and finance can value the result.
The exact boundaries vary by vendor, but buyers evaluating ERP for elevator manufacturers should understand these core modules:
General ledger, accounts payable and receivable, cash, job cost, tax, fixed assets, financial reporting, and period close.
Quotes, customers, sales orders, promised dates, commercial terms, invoicing, and order status.
Controlled part numbers, revisions, assemblies, quantities, units, approved sources, and product cost.
Requisitions, purchase orders, approvals, supplier commitments, receipts, invoice matching, and spend history.
On-hand quantity, location, allocation, lot or serial traceability, cycle counts, transfers, and inventory valuation.
Material requirements planning, work orders, routings, work centres, capacity, dispatch, labour reporting, and completion.
Inspections, nonconformance, corrective action, warranty, service records, and product traceability.
Permissions, audit history, operational reporting, master-data controls, and consolidated multi-site visibility.
Most custom cab shops need the financial backbone. Accounts payable, accounts receivable, general ledger, purchasing history, payroll interfaces, job-cost reporting, and inventory valuation remain useful whether the shop makes one design or a thousand. Shops that stock sheet, extrusion, hardware, lighting, or standard subassemblies may also use inventory, receiving, and replenishment heavily.
Usage becomes less consistent in product configuration, master production scheduling, material requirements planning, and repetitive work-order control. Those modules assume that an approved item, bill of materials, routing, quantity, and due date can become a dependable planning signal. In a custom elevator cab job, field dimensions, architectural comments, finish selections, engineering decisions, and change orders can alter that signal before fabrication.
A shop may technically own those ERP modules yet bypass them for day-to-day coordination. The estimator works in one workbook, drawings move through email, the buyer keeps a shortage list, and the production meeting maintains the real priority sequence. The ERP receives the order or cost after people have resolved the ambiguity elsewhere.
That is not proof that ERP failed. It means transaction control and project coordination are different jobs. The elevator cab project stages guide shows the handoffs a cab shop must control around the financial record.
A standard ERP bill of materials works best as a controlled recipe: make item A from known quantities of items B, C, and D using a known routing. A custom elevator cab bill of materials often begins as a commercial interpretation of incomplete documents. It changes as survey conditions, submittal comments, final dimensions, finish approvals, and fabrication decisions become known.
The problem is not merely that every job has different parts. The effective scope can change while estimating and engineering are underway, and each change can affect material, labour, vendor quotes, lead time, and contract value. Releasing an early bill of materials into material requirements planning can create false demand; waiting for perfect information can hide long-lead exposure.
Engineer-to-order control therefore needs a chain of evidence before the ERP transaction: quoted baseline, survey facts, drawing revision, customer response, change order where required, final estimate, and fabrication release. The submittal approval process explains why an approved drawing and commercial authorization are related but not interchangeable. The cab estimating guide explains how to preserve the cost baseline.
Record each BOM line, its quantity, source, material cost, labour hours, assumptions, and supporting quote.
Identify what changed and whether it changes material, labour, price, or schedule.
Approve additions or credits through a change order and update the final estimate.
Only the accepted revision and authorized bill of materials should drive purchasing and fabrication.
There is no universal winner. A full ERP can be the right foundation, especially when accounting depth, inventory valuation, repeat production, or multi-plant control is non-negotiable. A smaller shop may accept spreadsheets, while another may pair ERP with a purpose-built coordination layer.
| Decision | Full manufacturing ERP | ERP plus coordination layer | Spreadsheets and email | Purpose-built system |
|---|---|---|---|---|
| Engineer-to-order fit | Possible with careful configuration, project manufacturing modules, and disciplined master data. | ERP controls transactions; the second layer controls evolving scope and handoffs. | Flexible, but relationships and release rules depend on people. | Strong when its native workflow matches the cab shop. |
| Implementation effort | Usually the broadest process, data, training, and migration effort. | Requires clear ownership and defined boundaries between systems. | Low initial setup; continuing maintenance and reconciliation remain manual. | Narrower than full ERP, but operating practices still need agreement. |
| Drawing and revision control | Varies; often needs product lifecycle management, document control, or customization. | Handled in the coordination layer, with release status passed to ERP. | Folders and naming conventions are easy to bypass. | Can model submittals, revisions, change orders, and release directly. |
| Accounting depth | Strongest option for ledgers, valuation, close, controls, and consolidation. | Accounting remains in ERP, where it belongs. | Requires separate accounting software and duplicate entry. | Usually shallower; verify whether accounting is included at all. |
| Who it suits | Larger or repeat-production operations needing financial and plant control. | Cab shops that need ERP control without forcing unfinished scope into it. | Small teams with low volume and tolerance for manual control. | Teams whose main gap is an industry-specific job workflow. |
A real ERP is better at accounting, inventory valuation, and multi-plant repeat production. A shop that needs those capabilities should buy one. For a closer look at the manual alternative, read the comparison of spreadsheets, whiteboards, and email.
The clean boundary is based on ownership, not on copying every field both ways. ERP should own customers used for invoicing, suppliers, financial dimensions, purchase orders, receipts, inventory movements, invoices, payments, and the general ledger. The coordination system should own the evolving job context: survey evidence, estimate versions, drawing revisions, customer decisions, change orders, approvals, and release status.
A practical flow sends an approved customer and contract reference into ERP, then sends an authorized bill of materials or purchase request only after the release gate. ERP returns purchase-order, receipt, cost, and invoice status against a shared job identifier. Exceptions need visible ownership; an integration must not silently turn a superseded drawing into current demand.
Build It Track It does not have accounting or ERP integration today, and no integration ships at launch. Integration belongs to future ERP-adjacent work and must be designed around the systems a manufacturer actually uses. The CAD-to-ERP workflow guide examines the same release boundary without claiming that a drawing can safely generate a production BOM by itself.
Build It Track It is not an ERP. It is a pre-launch project-management system for elevator work, with launch planned for Q3 2026.
Available today, Build It Track It covers the coordination layer: a job record moving through a twelve-stage pipeline; role-based access; survey assignment through secure links; project email, communications, and attachments; estimating with a rate library; contracts and e-signature with a locked, hash-verified PDF; engineering drawing revisions, change orders, and a Final for Record lock; and signoff. A person enters every bill of materials line. Standard lines resolve material cost and labour hours from an approved rate-library item, while custom lines require a vendor quote.
Build It Track It does not generate a bill of materials from options, dimensions, drawings, or CAD. Purchasing, purchase orders, an inventory ledger, capacity planning, production scheduling, delivery-date scheduling, installation, and closeout are planned at MVP tier for the Q3 2026 launch, but they are not available today. Build It Track It does not provide accounting or connect to an ERP system today.
That Q3 2026 launch plan covers all twelve stages, including the ERP-adjacent scope of purchasing, inventory, capacity, and scheduling; it does not make Build It Track It a financial ERP. Uploaded drawings are stored as attachments, and Build It Track It does not parse, import, or export DXF or DWG files. CabStudio, a planned 2027 design initiative, is later roadmap work and is not a launch capability.
The useful comparison is therefore not Build It Track It versus every ERP module. It is whether the cab shop needs a controlled engineer-to-order record beside its transactional systems. Review the Build It Track It platform and the manufacturer roadmap with that boundary in mind.
An elevator manufacturing ERP system connects financials, sales orders, purchasing, inventory, bills of materials, production, job cost, and reporting. It is strongest at controlling transactions and resources; custom elevator cab scope, drawings, and approvals may still require a separate engineer-to-order coordination process.
The best ERP depends on the manufacturer's accounting requirements, inventory complexity, production model, number of sites, existing systems, and ability to maintain master data. A cab shop should test real engineer-to-order scenarios, including an incomplete bill of materials, a revised drawing, a change order, a long-lead purchase, and the resulting job-cost entries.
Standard ERP planning expects a controlled item, bill of materials, routing, quantity, and due date. In engineer-to-order manufacturing, survey findings, submittal comments, finish decisions, dimensions, and change orders can alter those inputs before release, so early planning can create false demand and late planning can conceal lead-time risk.
Some ERP products offer document control or connect to product lifecycle management systems, but capability varies. A custom elevator cab shop must verify that drawing revisions, customer responses, change orders, final estimates, and fabrication release remain linked rather than treating an attachment as proof that scope is approved.
ERP is the stronger choice for accounting, inventory valuation, purchasing transactions, and repeatable production control. Spreadsheets are flexible and inexpensive to start, but revision rules, dependencies, permissions, and reconciliation rely on people; some shops therefore use ERP for transactions and a separate coordination layer for engineer-to-order work.
ERP should normally own financial records, suppliers, purchase orders, receipts, inventory movements, invoices, and the general ledger. Elevator project software can own survey evidence, estimate versions, drawing revisions, customer decisions, change orders, and release status, with both systems using a shared job identifier and explicit handoff rules.
No. Build It Track It is a pre-launch elevator project-management system, with all twelve stages planned at MVP tier for Q3 2026, including purchasing, inventory, capacity, scheduling, installation, and closeout. It is not a financial ERP and does not connect to accounting or ERP systems today.
Purchasing, inventory, capacity, and scheduling are ERP-adjacent areas planned at MVP tier for the Q3 2026 Build It Track It launch. They are not available today, and Build It Track It is not positioned as a replacement for financial ERP.
Bring the ERP, spreadsheets, drawing register, and handoff process your cab shop uses. We will show exactly where Build It Track It fits and where it does not.
Request a demo