How TentTally works

No — you can import your whole catalog from a CSV file, or connect Square and pull your catalog straight from there, including prices, costs, and SKUs. Stock counts come over separately once you turn on Square inventory sync.

A SKU is your own product code — totally optional. It's how TentTally tells two similar products apart (like two sizes of the same print) and how Square catalog imports match up existing products.

That SKU was already in use by another product in TentTally, or your code disagreed with what's in Square. The product still imported fine — only the code was skipped. Set it by hand on the product's edit page.

You choose up front, per import: skip it, or update the existing product. Matching is done by SKU first, then by name.

Any column in your file that isn't a field TentTally already recognizes becomes a custom attribute on the product.

Groups bundle different formats of one design (say, an image sold as an 8x10, an 11x14, and framed) under one name in your catalog view, while still reporting on each format separately. When importing from Square, you choose whether each item's variations become separate products, import as one parent product only, or are skipped.

Categories organize your catalog and your reports — the Category report totals sales by category. Groups are just a display convenience for formats of one design — they don't affect tax or reports.

There's no delete. Archiving hides a product from your active catalog and frees up its SKU for reuse, but keeps its sales history — and its name in past reports — intact.

Yes, on a phone or tablet with Square connected. In the Order Builder, tap Charge with Square: it opens the Square Point of Sale app with the cart total filled in, and once the payment goes through you're brought back to TentTally with the sale recorded — items, discounts, and the Square transaction ID. Square receives the total, not an itemized order, and these card sales don't currently deduct TentTally stock. Beyond that, TentTally pulls your catalog and inventory counts from Square and can push stock counts back after a production batch; it never changes your Square prices or items.

Yes — pick a Square location under Settings → Integrations. Sync won't run without one selected.

TentTally automatically pulls Square's inventory changes for a market roughly two hours after the event ends — no one has to trigger it.

TentTally can push your new count back to Square as an absolute physical count, not an adjustment — it overwrites whatever Square had.

If Square reports zero stock for an unusually large number of products at once, TentTally assumes something's wrong on Square's end and skips the sync rather than zeroing out your inventory.

No — one Square merchant account can only be linked to one TentTally organization at a time.

Items with a single variation in Square sync automatically. Items with several variations under one Square item (like three sizes) are skipped for inventory sync, because TentTally can't tell which variation a single local stock count belongs to — importing those variations as separate products avoids that.

Products you already imported, and their SKU links, stay as they are. Your chosen location, auto-push setting, and sync scope are cleared.

Quick Entry is for ringing up a single item fast. Order Builder is for a multi-item cart — when a customer's buying several things at once, possibly with a discount.

Yes — a flat amount or percentage off a single line item, or off the whole cart, each with a required reason, entered by hand at the time of sale. For a recurring deal like "3 for $2," set up a pricing rule instead — see the next question.

Yes — under Products → Pricing Rules, set a quantity and price for a product, a group, or a whole category. At checkout, a qualifying cart shows the discount as a suggestion, and you choose whether to accept it — it's never applied without a tap. A line can't carry both a manual discount and a pricing-rule deal at the same time; adding one removes the other.

Use Custom Orders — it tracks the customer's contact info, a deposit if you took one, a due date, and can reserve inventory for it ahead of time.

TentTally checks, in order: that market day's own rate if you set one, then the market's rate, then your default rate (Settings → Tax). One rate applies to the whole sale. A zero rate is valid and won't be treated as "unset."

Inclusive treats your sale price as already including tax. Exclusive adds tax on top. Changing the setting isn't retroactive — past sales keep whatever mode they were recorded under, which is why the tax report flags a period that straddles a mode change.

Order Builder items in one cart post as a single transaction. Quick Entry items post individually, one per tap.

Edit or delete it from the Sales Log. Deleting posts a reversing entry to the inventory ledger rather than erasing anything, so you may see two lines for it afterward — that's correct, not a double-count.

There's no separate "refund" feature. Delete the original sale, then log it as a market return so the stock comes back.

A market return is a one-off "these came back" entry tied to a specific sale. The load workflow's own returned-count field is part of the packed/sold/returned tally for that market's load — use whichever one matches how you're already tracking that market.

It adds units to that product's on-hand stock count — log a batch every time you finish a crafting run.

Set a reorder point (and optional reorder quantity) on a product, and it flags as low stock once on-hand quantity drops to or below that point.

Inventory tracks finished, sellable units on hand. Cost materials are the raw supplies behind a product's unit cost and don't carry their own stock count — but changing a material's cost only changes what future products cost, not past ones.

On Hand is your physical count. Available to Sell subtracts stock already reserved by open custom orders, so the two numbers can legitimately disagree.

Yes — give the market its own rate, and optionally override it for a single market day. Either one takes precedence over your default rate.

Recording what you actually packed and brought to a market — not just what sold. Converted loads give the Smart Packing Estimator sell-through, trend, and seasonality to work with.

It starts from what sold at your recent markets at that venue, so it has suggestions as soon as you have sales there. Once you use Load Tracking — record what you packed, what came home, and convert the load to sales — it also factors in sell-through, recent trend, and seasonality, weighting recent markets more heavily. Confidence grows with the number of markets it has to go on.

Best Sellers (top movers), Category (sales by category), Profit (margin per product), Tax (what you owe, by market/category/rate), Payment Methods (cash vs. card vs. other), and Market Summary (one market's full recap).

That's by design — each sale locks in the cost, tax rate, and tax mode at the time it happened, so past reports aren't rewritten by later catalog edits.

That's expected — archiving only hides a product from your active catalog. Its historical sales keep their name and figures.

Yes, as CSV, from each report page.

Yes — reports let you exclude specific events from the numbers.

Owner has full access, including account and team settings. Member has full day-to-day access but can't change account or team settings. Cashier is restricted to the sale-entry screen and their own profile only — no dashboard, reports, product list, or market setup — and cost and margin data are stripped from what a cashier can see, not just hidden in the UI.

No — each person is tied to one organization, enforced at the database level. There's no switching between businesses on one account.

Only the owner. There's exactly one owner per organization, and ownership can't be transferred in-app yet.

Yes — each person has their own login and their own layout preferences, so switching people on the same tablet means logging out and back in, not just switching tabs.