Product editor

A React block (a whole screen) in Beamline's Shop app.

A product being made in a shop's back office, every value read as text at rest. The variant grid, grouped by the first option, lists each combination with its photo, SKU and a price per currency; a missing price reads "Add price" in its cell, each group counts its missing prices, and Publish waits beside a count that opens the first variant still missing one. A value becomes a field only where it is clicked (Enter saves, Escape puts it back). The options show as tags and open for editing on demand; renaming one keeps what was filled in. Beside the grid, the open variant: whether it is created, its photos picked from the product's own, its SKU and prices, and its inventory parts as links (a hint says creating variants creates no stock). Published, everything reads only.

Use it for

  • Creating a product whose options multiply into variants, each priced in several currencies before it can publish.
  • Any catalogue entry built from a cross product of choices (sizes × colours, plans × regions).

Not for

  • One stock item and its counts (inventory-item).
  • A shopper choosing a variant (a product page).

Anatomy

  • header: title (edited in place), Draft or Published, what blocks Publish (a button to the first variant missing a price) or Ready to publish, Publish
  • variants: count of combinations and how many will be created, Edit options; the options as tags (their names and values as fields while editing, Add option, each option's menu)
  • grid: grouped by the first option with each group's variant count and missing prices; each row's photo and name (opens it), SKU and a price per currency as text that edits in place; a combination not created reads "Not created" with dashes
  • the open variant: its name and Don't create / Create it; photos picked from the product's own (2 of 4); SKU and prices editable in place; inventory parts as links with the no-stock hint

States

  • missing prices
  • combination not created
  • nothing to create
  • ready to publish
  • editing options
  • editing a value
  • invalid price
  • published
  • no media to pick
  • no parts
  • phone: the grid without SKUs, the open variant under it

Keyboard

  • Tab through the title, Edit options, then each row's name (Enter opens it), SKU and prices; Enter or Space on a value edits it, Enter saves, Escape puts it back; Space toggles a photo

Props

PropTypeDefaultDescription
product (required)ProductDraft—
onProductChange((p: ProductDraft) => void)—
currencies (required)string[]—Currencies every variant is priced in.
onPublish(() => void | Promise<unknown>)—
partHref((inventoryId: string) => string)—Where an inventory part opens.
variantstring | null—The open variant, by its option values joined with " / ".
defaultVariantstring | null—
onVariantChange((key: string | null) => void)—
classNamestring—Classes on the documented visual root; no override by default.
styleCSSProperties—Inline styles on the documented visual root; no overrides by default.
refRef<HTMLDivElement>—Receives the documented native target or imperative handle; omitted by default.

Built from

Dependencies

lucide-react

Import

import { ProductEditor } from "@beamline/product-editor";

Get it

Product editor is part of Beamline UI. Install the parts you need in your React app as compiled packages or editable source. Get Beamline · Connect your agent

More in Shop

  • Category manager: A shop's product categories, nested and ranked. Each category moves up, down or into another from its menu, and every move gets its own receipt (saving…
  • Inventory item: One stock item in a shop's back office, apart from the variants that sell it (how many each uses per unit). Stock per location as stocked, reserved and…
  • Plan comparison: Plans side by side against every feature: prices that roll between monthly and yearly, the current and recommended plan marked, a header that stays in…
  • Step form: The finished frame for any multi-step form you compose — onboarding, intake brief, questionnaire, booking, application: a wide card with progress, the…
  • Orders admin: A shop's order desk: today's orders and revenue, quick filters for what needs doing (to fulfil, unpaid, returns), a virtualised orders grid, and the…
  • Order detail: One shop order with payment and fulfilment as two separate lanes. The header says where each stands (paid, partly paid, awaiting, refunded; not…
  • Order board: A shop's orders as cards in its columns, on the shared kanban with drag and keyboard moves. Each card: number, estimate or work order, customer, vehicle…
  • Order composer: An order made inside a support ticket: products found by name, each variant with its stock drawn and said (in stock, none, oversold, not known) and the…
  • Draft orders: A draft order made for a customer in a shop's back office that reads like the order it will become. The lines lead: each with its variant and SKU or…
  • Order changes: What happens to a shop order after it's placed. Edit: the order as it stands beside the requested version, each line marked new, changed (old → new…
  • Special orders: Customers' special orders as demand to buy for, per outlet: To order apart from Ordered; each product's demand, what is reserved, incoming and on order…
  • Order history and fills: Every order the account placed and every fill it got, for a period: totals for volume, fees, fill rate and maker share; orders with their status and how…
  • Order ledger: Purchase orders as money. Each order's spend is drawn against its approved total (paid, billed, pending, what is left, and any overrun past the end…
  • Ticket orders: A customer's orders inside a support ticket, each action's effect said before it's done: orders and drafts kept apart, a paid draft shown once as its…
  • Record search: One search across connected records (customers, vehicles, orders) by name, phone, plate, VIN or order number. What the words look like is said (info)…
  • Return queue: A queue of return cases. Search by return, order or customer, exactly (the default) or loosely; status tabs with counts, Requires attention first; a date…
  • Return case: One return as one place where every act is its own. The return, its order (linked out) and the customer on three cards; the stage said on its tone. Items…
  • Return request: Staff start a return from an order, and edit the reasons customers pick. New return: the order's lines as a checklist, each with its variant, price and…
  • Purchase orders: A salon's purchase orders, received: the orders down the side, the chosen one beside them. Each line still due reads as a strip of received, this…
  • Print quote: A print shop's quoting in three places. Quote: a group of garments that share one imprint and one quantity break, the group's pieces counted together and…
  • Service estimate: An estimate for one vehicle. Services added from the catalogue (one not listed for this vehicle said on warning, fit unknown said); each with its lines…
  • Job card: A technician's repair order, phone-first. The vehicle, the customer and when it's due in words (due at, due in, overdue by how long); an offline copy…
  • Parts tracker: Parts across a shop's work orders: each with its number, the order and vehicle, supplier, quantity and cost (not known said), and where it is: ordered…
  • Visit board: The staff board for a walk-in queue: visits move from waiting through called and serving to done today. Arrival (here or on the way), the place in the…

Part of Beamline UI: polished, editable React components and complete screens for custom applications. Build your own style from any look; tokens, fonts, radii, motion; not only colours.