Back to field notes

Product

Automating the SKU: The End-to-End Product Creation Engine

How we are replacing manual B2B catalog management with an AI-driven system that handles everything from discovery to automated billing.

Nomu
Matt Dgn avatarMatt DgnCo-founder, Engineering3 min read

A founder recently told us it takes her team two days to list a single custom SKU. Between the warehouse measurements, the spec sheets, and the manual PDF generation, the process is a relic of 1990s procurement. Consumer commerce solved this a decade ago. B2B commerce remains a mess of fragmented data and broken web portals. We are building the engine to fix that.

Our V5 update moves the platform from a simple search tool to a full transaction engine. We are replacing manual billing with an automated flow. Instead of an operator manually generating an invoice, the system triggers the financial record and notification immediately upon product creation. This is the first step toward a liquid B2B market where procurement is as readable as a consumer storefront.

Key points

  • Automated billing replaces manual PDF generation
  • AI-readable product surfaces enable instant discovery
  • Mobile-first design for operators on the warehouse floor

The Top Version strategy

We have adopted a specific engineering philosophy as we scale the product engine. We are not aiming for absolute perfection in the interface. We are aiming for a version that is top. In early-stage engineering, the pursuit of perfection often leads to manual workarounds when the code fails. We want the opposite.

We need a system that is operational from day one, even if the feature set is lean. If the automated billing works for ten invoices without a human touching a keyboard, it is better than a perfect system that is not yet deployed. A top version is about operational insurance. If the data flows without manual intervention, the system is successful. This allows us to move fast without leaving a trail of broken manual processes behind us.

End-to-end AI creation

The core of the update is the AI-readable product surface. Most B2B catalogs are just digital filing cabinets. They store data, but they do not understand it. Our system ingests raw supplier data and structures it into a sellable product format automatically.

This goes beyond simple data entry. The system handles the mapping of industrial specifications to searchable attributes. When a warehouse operator scans a new item, the AI generates the listing, assigns the billing logic, and prepares the SKU for the storefront in seconds. The goal is to make the software invisible so the operator can focus on the physical goods.

The complexity of a B2B relationship should live in the backend logic, not the user interface.

The counter-argument

The obvious objection is that industrial products are too nuanced for an automated engine. Critics argue that custom pricing and complex technical specs require a human gatekeeper to prevent errors.

We disagree. The complexity of a B2B relationship should live in the backend logic, not the user interface. A buyer should not have to navigate a manual maze for every vendor they work with. Currently, a procurement officer spends nearly half their week just confirming that a SKU exists and the price is current. We are not removing the human expertise. We are removing the paperwork that gets in its way.

Closing the loop

We launch the new site in early July. It is built to be mobile-first, using depth and parallax to reflect the physical scale of the supply chains we manage. The goal is clarity. If a founder cannot understand the status of their inventory in one glance, the software is too complicated.

Frequently asked

Matt Dgn avatar

Matt Dgn

Co-founder, Engineering

Software engineer and Nomu co-founder building the storefront engine, the agentic commerce protocol layer, and the Next.js stack that powers consumer brands on the platform. Writes about commerce architecture, AI-readable storefronts, and the engineering trade-offs that decide whether a brand ships or stalls.