The catalog

Open Finance → Catalog. This page answers one question: what does your organization sell, and how much of it actually sold. Every row is a product — a service you set up in GIG, an item Stripe or your point-of-sale already knows about, a manual ledger entry, or a rolled-up family of ticket sales — with its units sold, its revenue, and when it last sold.

Plans and member enrollment live on a separate page now — see Finance → Memberships. This page is about what the business sells; that one is about who is subscribed.

The category bands

At the top of the page, revenue is grouped into bands like Show Tickets, Passes, Client fees, Bar & Retail, and Sponsorship & Grants, each broken into tiles for the individual products or ticket families underneath it. Every tile's total and share of revenue are calculated against the entire catalog, not against whatever you've searched or filtered — so a tile's percentage and its band's percentage always add up correctly. Choose a tile to filter the table below to that category; choose it again to clear the filter.

Adding a service

A service is a one-time item — sold once per purchase, not on a schedule.

1. Under Services, choose + New service.
2. Enter a Service name.
3. Enter its price, in CAD.
4. Choose Add service.

GIG creates the matching product and price in your connected Stripe account and lists it in the catalog. You need Stripe connected before this control is available.

Syncing from Stripe

Sync from Stripe pulls in products and prices that already exist in your connected Stripe account but weren't created from this page — from the Stripe dashboard, for instance — so the catalog reflects everything Stripe has, not only what was added here.

Assigning a category

Every product needs a category to leave the Uncategorised section at the bottom of the page — GIG's audit queue for sales nobody has filed yet. Choose the category pill on any row to reassign it. A product with no catalog row of its own (a name Square or Stripe reported that was never explicitly added here) can't be recategorized from the list — open its transactions instead and file it there, or leave it in the audit queue.

Clearing a category (choosing Uncategorised again) is not the same as never assigning one — it's a record that someone looked and decided it doesn't fit anywhere yet, and it goes back to the audit queue.

Opening a product's transactions

Choose any row to open every transaction behind its total — the same page a 1,300-line audit needs room for, not a popup. From there you can:

• Rename the product, if it's a group GIG created to combine several differently-named sales under one product (an "edit" icon appears next to the title). A product mirrored directly from Stripe or your point-of-sale can't be renamed here — its name has to match the processor's record, or the two would silently drift apart.
• Reassign the category on one transaction, independent of the product's own category. This is the correction of last resort: if a single sale was filed under the wrong product by whatever matched it automatically, your explicit assignment here always wins over the automatic match, on every later view of this page.
• See who bought it. Where the purchase is tied to a person in GIG, their name links to their profile. Where it isn't — a checkout Square or Stripe processed for someone not yet in your directory — GIG still shows the name or email the payment processor collected, so the row is never a blank dash when the processor itself knows who paid.

What rides along, and isn't a Stripe object

Three kinds of row appear in the catalog that were never created from this page, and none of them can be edited the way a service can:

• Manual ledger entries — money recorded by hand on a project's budget (a grant, a wire-transfer sponsorship) that never touched a payment processor. These show up so a sponsorship or grant is part of the sales picture, not missing from it; selecting one takes you to the budget line it actually lives on, since there's no transaction to drill into.
• Ticket sales, rolled up by family (for example, "Ticket Sales — Front Row") rather than every individual ticket type, so hundreds of near-duplicate ticket names don't drown the list. Selecting one opens the Ticketing report filtered to that family.
• Uncatalogued sales — anything your point-of-sale or Stripe recorded that was never explicitly added as a service and has no product of its own. These sit in the audit queue until you either assign them a category or leave them uncategorised on purpose.

What's deliberate here

• A sale only counts once it's actually paid. An abandoned cart or an open, unpaid invoice from your point-of-sale never appears as revenue here, even though the processor recorded it — GIG only counts a transaction once its payment has gone through (or been refunded, which still counts as sold). This is why the catalog's totals can be lower than a raw processor export.
• A ticket family's revenue is net of tax, matching how a point-of-sale export prices everything else on this page — comparing categories side by side wouldn't mean much if one used gross and another net.
• Reassigning a transaction to a different product doesn't move money anywhere. It only changes which catalog row that sale is counted under, for reporting. It has no effect on the payment, the buyer, or anything already reflected in Payments or Payouts.

What isn't answered here yet

Whether GIG can bulk-reassign more than one transaction at a time isn't covered — every reassignment described above is one row at a time.