Skip to content
BIKE.co

Platform · PLM

erp.io

Custom builds as a versioned bill of materials

PLM is the erp.io product lifecycle module, built for manufacturers. For a shop that does real custom builds, it holds the frame, the build kit and every component as a bill of materials you can version, compare and check for compatibility.

app.erp.io/service · plm · builds
Bill of materialsrev Arev B
  • Custom gravel build · 56BLD-0042 rev B
  • FramesetSteel · 56 · T47 · UDH×1
  • Groupset12s mech · 1× 40T×1
  • Rear derailleurUDH direct mount×1
  • Cassette10–51T×1
  • Wheelset700c · 12×142 / 12×100×1
  • Tires700×45 tubeless×2
  • CockpitBar 44 · stem 90 · internal route×1
rev B: cassette 10–52 → 10–51 · approved

A custom build is a product

Most shops do not need PLM. If your custom work is a few dream builds a year, a project in Projects and a spreadsheet will do. But some shops build bikes as a core part of the business: a house gravel build offered in five sizes, a frame builder's workshop, a shop that assembles a dozen custom road bikes a month. For them, each build is a product, and a spreadsheet stops being enough the first time a distributor discontinues a crankset halfway through a batch.

PLM treats the bike as a structure. The top line is the build. Under it sit the frame, the fork, the wheelset, the groupset and the cockpit. Under the groupset sit the shifters, derailleurs, crankset, cassette, chain and brakes. Each line has a quantity and a find number, and each part has a record of its own, with a part number, a classification and a revision history.

The PLM module was built for manufacturing teams, and it carries more than a shop will use. The parts that matter for custom builds are the structures, the variants, the rollups and the change history.

What PLM does today that fits a build shop

A selection of the live PLM module, chosen for custom builds.

erp.io

Multi-level structures

The build, its assemblies and their components, with quantities, units and find numbers, resolved down to the last bolt.

erp.io

Options and variants

Option sets such as frame size or drivetrain, with rules that say which options require or exclude others.

erp.io

A configurator that checks compatibility

Pick a combination and PLM says whether it is buildable, and names the rule that says it is not.

erp.io

Cost and weight rollups

Cost and mass rolled up from one resolution of the structure. Parts with no price or weight are counted as unknown, never as zero.

erp.io

Revisions and baselines

Revise a part or a build, freeze a baseline of the spec you sold, and compare two structures side by side.

erp.io

Where-used

Find every build that uses a part, which is the first question when a supplier discontinues it.

erp.io

Alternates and substitutes

Record parts that are interchangeable everywhere separately from a substitute approved in one position only.

erp.io

Change requests and orders

Change requests, change orders, deviations and approvals, so a spec change on a house build is recorded and signed off.

Sizing and compatibility as rules

Every custom build shop has a list of things that do not go together. A 12-speed chain on an 11-speed cassette. A flat-mount caliper on a post-mount frame. A 44mm head tube and a straight-steerer fork without the right headset. That list usually lives in the heads of the two people who have been building longest.

PLM's variants let you write those rules down. An option set is a choice the rider makes, such as frame size, drivetrain or wheel size. A rule says that choosing one option requires another, or excludes it, with a sentence explaining why. The configurator runs the rules against a combination and tells you whether it is buildable and which rule is in the way, so a junior mechanic spec-ing a build gets the same answer the senior one would give.

Sizing works the same way. The frame comes in sizes, and some components change with it: stem length, bar width, crank length, seatpost. Make them options, write the rules, and the structure for a size 54 differs from the one for a 58 only where it should.

Retail POSField serviceBIKE.co
Point of sale + hardware
Workshop tickets / jobs
Checklists with photos + signature
Scheduling + dispatch
Bike records + serials
Parts on the work order
Books, hiring, training

Categories, not products. Filled = yes, half = partly, dashed = on the BIKE.co roadmap.

Compare two builds

Compare the spec you quoted with the spec you built, or this season's house build with last season's, line by line.

Illustration · sample data

A custom build in PLM

How the parts of a build map onto the PLM model.

On the benchIn PLM
The build the rider orderedA top-level structure with its own revision
Frame, fork, wheels, groupset, cockpitAssemblies and components with quantities and find numbers
Frame sizes and drivetrain choicesOption sets
Things that do not fit togetherRequires and excludes rules, checked by the configurator
Build price and weightCost and mass rollups, with unknowns counted
A discontinued cranksetWhere-used, then a change order
The spec you soldA baseline you can compare against later

How PLM connects to Service

Today, it does not connect directly. PLM is a separate module in the suite. At present it asks for its own sign-in rather than using the suite hand-off the other modules use. A build structure in PLM is not linked to a Service work order, and Service has no parts inventory for PLM parts to match.

Half of that link now exists: work orders are live in Service as numbered jobs with line items. The other half is not. Parts inventory and purchase orders are planned for a later phase of the Service build. When they exist, the natural connection is a build BOM in PLM feeding the parts list of a build work order. That is a direction, not a commitment with a date.

What you can do today is keep the build itself in PLM, the schedule and people in Projects, the conversation in Chat, and the final safety inspection in a Service checklist, which is live. A rider picking up a custom build should get the same signed inspection PDF as any other bike.

FAQ

Questions shop owners ask

Does my shop need PLM?+

Only if custom or house builds are a real part of the business. For a few builds a year, a project in Projects is enough. PLM earns its place when you build in sizes and batches and need versions, compatibility rules and rollups.

Can PLM check whether components are compatible?+

Yes, if you write the rules. Option sets hold the choices and rules say which options require or exclude others. The configurator then tells you whether a combination is buildable and which rule blocks it.

Can I get a build price and weight?+

Yes. PLM rolls up cost and mass from the structure. Any part with no price or weight is counted as unknown rather than zero, so a total never looks complete when it is not.

Can I import my existing parts spreadsheet?+

Yes. PLM imports from CSV and Excel files, including files saved out of other systems, and reports what it mapped.

Does a PLM build create a work order in Service?+

No. Service work orders are live, but there is no link between PLM and Service today, and parts inventory is on the roadmap. The final inspection can be done with a live Service checklist.

Keep reading

Take in your next repair on BIKE.co.

30 days free, no card, every erp.io module switched on. Start with a request, end with an invoice.

Start free trial