Creating Products

Naming, pricing & packaging rules

The three core rule families — how a product reads, what it costs, and how it packs — and how you teach each one once.

Most of what you teach Tangerine Star falls into three families: how a product reads (naming), what it costs (pricing), and how it packs (packaging). Get these right once and every future order inherits them. You describe the change to Tory in plain language, or set the store-wide defaults on the Rules hub.

Naming

Vendors name products for their warehouse, not your shelf — ALL CAPS, stray symbols, sizes and pack counts jammed into the title. Naming rules turn that into names that read cleanly in your store.

Your store-default naming applies to every product and includes:

Remove all-caps — title-case the names
Remove special characters — strip marks like ™ © ® ℠
Append size to the name — optional, off by default

Vendor-specific cleanups — like stripping a vendor's product code out of the title — are set per vendor, because they're messy in vendor-specific ways.

Ask Tory the way you'd say it: "title case these names,""strip the SKU out of the title,""add the size to each name." She shows the before-and-after before anything changes.

Pricing

Pricing is a markup on cost plus a tail (how the price rounds). Your store default sets both — for example, a 2.2× markup ending in .99 — and applies to every product unless a vendor rule overrides it.

There's a priority to how a price is chosen:

Accept the vendor's price

If a vendor supplies the retail price and you've chosen to accept it, that price wins. See Vendors.

Apply a vendor pricing rule

Otherwise, if you've set a markup rule for that vendor, it applies.

Fall back to your store default

If neither is set, your store-default markup and tail do the work.

Try "mark these up 2.2x,""round prices to .95," or "price this vendor at 2.5x ending in .99."

Packaging

Vendors sell in cases and packs; you sell singles. Packaging rules capture that breakdown so your per-unit cost and inventory count land on the unit you actually sell — not the case.

A packaging rule describes how a purchase unit maps to sellable units:

Flat — one purchase unit is one sellable unit
Pack — a purchase unit contains a fixed number of sellable units
Case — a larger grouping, often of packs

Set it once for a vendor and every future order applies the same math automatically — no re-doing the arithmetic each time.

Say "these come 12 to a case,""this is a pack of 3," or "sold as singles."

See flat / pack / case worked through on a real order in the Jason's packaging-rules scenario.

Teaching once, applying forever

The point of all three families is the same: make a decision once, and have it stick. When you tell Tory to apply a fix to a whole vendor or your entire catalog, it becomes a rule — and the next order gets the same treatment without you lifting a finger. How far a rule reaches is up to you.

Decide how wide a rule applies — one item, one vendor, or everything — in Rule scope.

Store categories

Build the category tree your products roll up into — nest it to any depth, and let rules file incoming products for you.

Rule scope: merchant, vendor, PO & one-off

Decide how far a rule reaches — your whole catalog, one vendor, a single PO, or just this item — and know which rule wins when they overlap.