Skip to content

Product catalog

Turn a few partsinto a whole product catalog.

Each part gets a matrix of finishes, and one product code says which parts go in, how many and in which finish. Every code is a real product with its own price.

Your parts protected by an NDA.

Four uploaded parts

BodyBDY-01 · Injection molded
Light modulesLED-02 · PCB + LED
DiffuserDIF-03 · Molded acrylic
Base plateBAS-04 · CNC aluminum
LMP·H2·Q3·D2·B3

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

345.6Morderable finished products
from these four files

What it is

The catalog has two layers.

The first turns a part into every finish it can wear. The second turns those parts into a product.

Layer 1 · the part

Each part is a finish matrix

You upload a part once, and every combination of color, marking, size and packaging becomes its own reference. You can try the configurator on the variants page.

See the part configurator

Layer 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

How you start

From a CAD file to a delivered product.

Nothing special to begin: the first step is an ordinary part, quoted by an engineer.

  1. 01

    Upload each part of your product

    One CAD file per part. An engineer quotes each one by lot, exactly like a standalone part.

  2. 02

    Turn each part into a variant matrix

    Add colors, coatings, marking, sizes and packaging. Every combination becomes a real reference 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 products 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

Each code is one product.

A code decides which parts go in and how many, not just the finish: 81 ready-made builds here, 345.6M with the full matrices.

Code analyzer · Wall lamp

Type a code or click an option. Try

prefixLMP
BodyBDY-01 · Injection molded
3 of 6,400 finishes
Light modulesLED-02 · PCB + LED
1–3 per unit
DiffuserDIF-03 · Molded acrylic
optional part
Base plateBAS-04 · CNC aluminum
3 of 6,000 finishes
✓LMP·H2·Q3·D2·B3resolves to 1 orderable product · 4 of 4 parts345.6Morderable combinations · 81 ready-made builds shown

The real parser

The system a real catalog runs on.

The demo above is a scale model. This is the tool: a product broken into coded nodes — 7 element layouts, 69 function options, 14 finishes — and an analyzer that resolves one string into one product out of over 1.5 billion distinct assemblies.

The structure editor · sample product

Made to order, fulfilled from stock

We store your stock and ship it under your brand.

An encoded product can be produced, held and shipped on demand — a customer order becomes a shipped unit without a warehouse on your side.

To Amazon FBA

Palletized and labeled to Amazon’s inbound requirements, straight from our warehouse.

To your warehouse

In bulk or in kits, when you need it, in the packaging you sell in.

To the end customer

Shipped order by order from the minimum stock we hold for you.

A product catalog, defined

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

Two layersthe part’s finishes, then the product’s parts
One codewhich parts, how many, which finish
Every code is realpriced, orderable, made to order
Held & shippedto Amazon, your warehouse or the buyer

Questions

Questions about the product catalog

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 products, 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 product 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, colour, 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 product 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 labeled 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 on Amazon for four times what it costs to make.

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.

Get started

Upload your part and get its quote.

Upload one part or your whole BOM. You get a price and lead time in 24–48 h.

Get a quote →

Your parts protected by an NDA.