Creating Products

Reading & editing a product

The product page shows everything about one product — its identity, price, variations, rules, and history — and lets you edit most of it in place.

Every product has its own page — the single place to read what Tangerine Star knows about an item and to correct anything that's off. It adapts to the kind of product you're looking at: a standard product, a multi-SKU family, an assortment, a blanket SKU, or a child SKU within a family.

What's on the page

Reading top to bottom:

Title and summary — the product name, with its type, vendor, category, and price on one line.
Status strip — four quick stats: when it was Introduced, quantity On hand, Sales (30d), and whether it's Published to your point-of-sale.
Product info — the main editable card: name, description, identifiers, attributes, price, cost, quantity, and store category.
Published status — how this product stands in your PoS (in sync, changed, not yet published) with a button to push it.
Rules on this product — the rules that have actually operated on this item.
Variations — for families, the table of child SKUs (see below).
Sales Performance and Inventory activity — how it's moving.
Purchase Order History — every PO this product has appeared on.

Editing in place

There's no "edit mode" to switch on. Click any editable field and it becomes an input; press Enter or click away to save, or Esc to cancel. A pencil appears when you hover an editable field, and a green check flashes when a save lands.

Editable fields in Product info include:

Name and Description
Identifiers — UPC, TS SKU, and Vendor item ID (the Clover ID is shown but managed by publishing, not edited here)
Attributes — Size, Color, Style
Price (retail), Cost, and Quantity on hand
Store category — a searchable picker over your category tree

Cost carries a reminder: "Catalog default — does not change historical PO costs." Editing it sets the going-forward catalog cost; it never rewrites what a past order actually cost you.

A few things are read-only on purpose — the product's Type, its Source (how it entered your catalog: created manually, from a PO, a Clover import, and so on), and its Status.

The canonical identity chip

Under the identifiers, a colored chip shows the product's canonical barcode — the one value Tangerine Star treats as the real scan target. Its color tells you how trusted that identity is, from a merchant-authored or vendor-printed code (most trusted) down to an unvalidated import.

Click it to open the Canonical Identity history: the current scan target, the legacy UPC and TS SKU fields kept for reference, and a timeline of every identity the product has ever carried. Nothing is thrown away — you can always see where a barcode came from.

This is why we say never guess which barcode is real. The chip is the answer, and its history shows the reasoning. More on how that value is chosen in Identifying reorders & duplicate UPCs.

Working with variations

For a multi-SKU family or an assortment, a Variations table lists every child SKU with its own Price, Cost, On hand, On order, UPC, TS SKU, and status. You can:

Edit any child field inline — the same click-to-edit as everywhere else.
Set the default child — the star marks which variation is the "face" of the family.
Ask Tory to edit the whole set at once — the bar above the table takes plain-language requests like "round all prices to .95" or "add the size to each name," previews the before-and-after for every child, and applies it once you confirm.

On a product page, Tory handles renaming and repricing child SKUs today. For other changes to a child (like its category), edit it inline in the table.

Publishing and history

Published status shows whether this product matches what's live in your PoS, and flags exactly which fields have drifted. Buttons let you Push to Clover or Update in Clover.
Purchase Order History lists every PO the product has been on — PO number, vendor, date, quantity ordered vs received, and cost — so you can trace an item back to where it came from and what you paid over time.

Building or restructuring a family? See Multi-SKU products for how child SKUs are created and managed.

The Rules hub

One page that shows every automated decision Tangerine Star makes for your products — set your store defaults, and see every vendor exception.

Vendors

Your supplier network — where each vendor's pricing, naming, packaging, and category rules live, and how to tune the relationship.