Product catalog

A few parts in. A whole product catalog out.

Upload the parts of your product. Each becomes a matrix of finishes; a second parser encodes which parts go in, how many, and their finish as one orderable code. Every combination is a real, priced SKU — and we hold the stock and ship it for you.

Start with one part →See the parser in action ↓

Four uploaded parts

BDY-01LED-02DIF-03BAS-04
LMP·H2·Q3·D2·B3

One code decides which parts go in, how many, and their finish — one orderable product SKU.

Quick definition

A product catalog on OperGo is built from two layers of encoding. The first turns each individual part into a matrix of finish variants — every color, marking, size or packaging a real, priced SKU. The second combines those parts into a finished product, encoding which parts go in, how many of each, and which finish, as a single product code. A simpler build resolves to a shorter code with fewer parts; a richer one adds them back. From a few uploaded files you get a whole catalog of orderable finished products, made to order and fulfilled from stock — with no new files or tooling per variant.

How you start

Five steps from a CAD file to a fulfilled product.

  1. 01

    Upload each part of your product

    One CAD file per part. Each is quoted by lot and priced by a real engineer, exactly like a standalone part — nothing special to start.

  2. 02

    Turn each part into a variant matrix

    Add colors, coatings, marking, sizes and packaging. Every combination becomes a real SKU with its own price and lead time — grouped as variants, not separate uploads.

  3. 03

    Encode the product with the parser

    The product parser writes which parts go in, how many, and their finish as one product code — e.g. LMP·H2·Q3·D2·B3. Leave the diffuser out or drop to one light and the code gets shorter.

  4. 04

    Order any finished combination

    Every code the parser can generate is a real, orderable product. Millions of finished SKUs come out of a handful of files, with no new tooling per variant.

  5. 05

    We hold stock and fulfill

    We keep the material and finished stock and ship on your behalf — palletized to Amazon FBA, to your own warehouse, or drop-shipped to the end customer.

The product parser

Simple or complex — one code, one product.

A worked example, in a small replica of the code analyzer we actually run: four uploaded parts, one encoded product. Type a code and watch it resolve node by node — or click the parts and read the SKU that comes out.

Code analyzer

Wall lamp — one code, 4 of 4 parts in this build

prefixLMP
BodyBDY-01 · Injection molded
3 of 6400 finishes
Light modulesLED-02 · PCB + LED
1–3 per unit
DiffuserDIF-03 · Molded acrylic
optional part
Base plateBAS-04 · CNC aluminum
3 of 6000 finishes
✓LMP·H2·Q3·D2·B3resolves to 1 orderable product SKU · 4 of 4 parts

Type a code or click an option. Try

345.6Mfinished-product SKUs

The same code decides which parts go in and how many — with or without the diffuser, one to three lights — not just the finish. Pick from what's shown and you already have 81 ready-made builds; open up every part's full finish matrix and this one product spans 345.6M orderable combinations — each a real SKU, from the same four uploads. No new files, no new tooling.

The real parser

You just used a scale model. This is the system a real catalog runs on.

The same two-layer encoding and the same left-to-right resolution, in the actual tool — a product broken into coded nodes (8 element layouts, 69 function options, 14 finishes) and a code analyzer that resolves one string into one exact product out of over 1.5 billion.

OperGo catalog structure editor: a product defined as a tree of coded nodes — Elements, Function (69 options) and Finishes (14).

01A product as a tree of coded nodes

8 element layouts, 69 function options, 14 finishes — each carrying its own code and cycle time. This structure is what the whole catalog is generated from.

01 / 03

Two parsers, one product

The part is encoded. Then the product is encoded.

Parser 1 · the part

Each part is a finish matrix

One uploaded part, every color / marking / size / packaging combination generated as its own real SKU. This is the live configurator you can try on the variants page.

See the part configurator →
Parser 2 · the product

The product combines parts

A second code encodes which parts go in, how many, and their finish. Multiply each part’s matrix by every structural option and one product spans millions of orderable combinations.

See how it’s assembled & tested →

Made to order, fulfilled from stock

We hold the stock and ship it — you never touch a box.

The whole point of encoding the product is that it can be produced, held and shipped on demand. We keep the material and finished stock and fulfill on your behalf, so a customer order turns into a shipped unit without you managing a warehouse or chasing vendors.

To Amazon FBAPalletized and labelled to Amazon’s inbound spec, straight from our facility.
To your warehouseBulk or kitted, on the cadence and packaging you sell in.
To the end customerDrop-shipped per order — no stock sitting on your side at all.
See a real Amazon SKU →Delegate the whole product

The product catalog, answered

What's the difference between a part variant and a product configuration?

A variant is one finished version of a single part — the body in matte black, say. A product configuration combines several parts, each with its own variant and quantity, into one finished unit: the whole lamp. The first parser encodes the part; the second encodes the product built from those parts.

Can one product code include or leave out whole parts?

Yes — that is the point of the second parser. A code decides which parts are in the build and how many of each, not just their finish. A wall lamp with no diffuser and one light resolves to a shorter code with fewer parts; add the diffuser and two more lights and the same definition produces a richer product. Simpler and more complex versions live under one encoding.

How do you get to millions of combinations from just a few parts?

Because the options multiply. If a few parts each carry a finish matrix of thousands of variants, and the product can also vary how many of each part go in and whether optional parts are present, the finished product spans the product of all those numbers — quickly hundreds of millions of orderable SKUs, all generated from the same handful of uploads.

Do I have to upload every combination separately?

No — that is the whole point. You upload each part once and define its finish attributes and how it can be used. The parser generates every valid combination as a real SKU on demand, so you never manage thousands of files by hand.

Can I define my own encoding scheme?

Yes. The code is yours to structure — by typology, color, size, quantity, or whatever attribute matters to how you sell. The parser just enforces that scheme consistently across every part and every combination, so the same product always resolves to the same code.

Is every generated code actually a real, orderable product?

Yes. Every combination the parser can produce is a genuine SKU with its own price and lead time, quoted and made to order — not a mock catalog. You order any code and it gets produced, assembled and finished to that exact spec.

What's the minimum order for a single variant?

Each variant is priced by lot, like any OperGo part, so there is a per-combination minimum rather than one big minimum for the whole catalog. Your engineer sets it per part at quoting, based on the process and finishes involved.

Can you hold stock and fulfill to Amazon or my customers?

Yes. We can keep the material and finished stock and fulfill on your behalf — palletized and labelled to Amazon FBA’s inbound spec, shipped to your own warehouse, or sent straight to the end customer. One reference ran exactly this model, selling at 4× its production cost on Amazon.

Is the manufacturing process locked once the product is defined?

No. The process behind each part — CNC, injection molding, sheet metal — is never locked in. As volume grows, an engineer can move a part to a more cost-effective process without changing your product codes or how you order them.

Variants & finishes →

The part layer — try the live single-part configurator.

See it on a real catalog →

A designer switch brand runs over 1.5 billion combinations on this exact system.

Stock & fulfillment →

The layer above: every code held as real stock and shipped on your behalf.

Ready? Go.

Get a price an engineer will stand behind.

Send one part or your whole BOM. An engineer reviews it with the shop floor and sends back a real price, a real lead time and free DFM notes.

Get my quote →

Free account, no commitment · NDA signed before you upload.