Catalog · Catalog Studio
Give the counter one dependable product definition.
The same item should not carry a different barcode, tax code or margin story every time it is sold.
This is a capability inside Lightning Pharos, not a separate product.
Publish a product, variant and customer-group price.
01 · What ships
The complete working surface.
Products, variants, price lists, and the identifiers the counter uses.
- 01
Products with variants, SKU, barcode, units, media, options, and attributes
- 02
List, MRP, and cost price held separately on the sellable record
- 03
Tax-code links keep HSN or SAC treatment with the tax definition
- 04
Customer-group price lists and product kits
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Publish a product, variant and customer-group price.
- 02 / 03
Governed event
The catalog version becomes the record used by selling and stock workflows.
- 03 / 03
Connected result
Search, billing, tax and margin all begin from the same definition.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
Price lists do not yet have store or channel scope or effective-date scheduling.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system