How to run a storewide sale and per-booth vendor sales at the same time — without the math going sideways

Antique malls run two completely different kinds of sale events. The mall manager runs a storewide event (“10% off everything for Memorial Day weekend”), and individual booth owners run their own per-booth sales (“Booth 47 — 25% off all glassware this month”). On a busy Saturday those two things absolutely will collide on the same ticket — the question is whether the math comes out right and whether anyone can audit it later.

Vintique stacks them automatically, in the right order, and breaks each layer out separately on the receipt and on the per-vendor settlement report. Here’s how it works in practice and how to plan an event weekend without spreadsheets.

The stacking order

For every line item on every ticket, Vintique applies discounts in this order:

1. Vendor sale first. If the booth that owns the item has its own sale percent set, that comes off first. (Vendors can self-edit their own sale percent from the My Sales dashboard without an admin handoff — useful for a vendor-led promotion.)

2. Storewide percent next. If a storewide event is active, that comes off the vendor-discounted price. Storewide stacks on top of vendor, not the other way around — this matters because vendor consignment math reads the post-vendor-discount price as the dealer’s gross, then applies the storewide discount as a mall-bourn cost.

3. Cashier discount last. Any one-off cashier adjustment (“dollar off because the corner is chipped”) comes off last.

What shows up on the receipt

Receipts show every layer. The shopper sees:

• The original tag price.
• The vendor discount line, with the vendor’s sale percent.
• The storewide discount line, with the storewide percent.
• Any cashier discount line.
• The final price.

This matters for two reasons. First, customers like to see the “savings” itemized. Second, when a vendor calls the office a week later asking why their item rang at a different price than they expected, you have a receipt that explains itself without a phone call.

What shows up on the settlement report

The end-of-month per-vendor settlement breaks the same layers out for the vendor:

• Gross sales (post-vendor-discount, pre-storewide).
• Storewide discount applied (mall-bourn).
• Consignment fee (per the vendor’s rate).
• Net payout to vendor.

Because storewide is mall-bourn, vendors can run their own sale on top of a storewide event without losing money to the discount. They choose a vendor sale percent that makes sense for their inventory, and the storewide is the mall’s contribution on top.

Planning a holiday weekend

1. Set the storewide event a week ahead. Settings → Sale events → New storewide. Pick start and end timestamps, percent off, and any item exclusions if you have categories you don’t want on sale (e.g. consignment exclusions for gift cards).

2. Email the vendors. Tell them the storewide is coming, the percent, and that they can run their own per-booth sale on top from their My Sales page.

3. Vendors set their own sales (or don’t). Vendors who want to participate set their own sale percent. Vendors who don’t, do nothing — their items still get the storewide discount, but at the dealer’s full gross.

4. Open Saturday. The register handles the math automatically on every ticket. Cashiers don’t apply discounts manually; they just ring the sale.

5. Close out Sunday night. Daily reports show the weekend’s totals broken out by discount layer. The per-vendor settlement at month-end will reconcile cleanly because every discount layer was already attributed correctly at the time of sale.

Where stacked sales tend to go wrong

• Cashier-applied discounts that aren’t recorded as such.

  On systems where the cashier types in a new price instead of using a discount field, the discount layer is lost — vendors see only the lower gross and assume they got shortchanged. Vintique forces every discount through a typed field; the original tag price is preserved.

• Storewide deducted from vendor share. Some POS configurations push the storewide discount onto the vendor, which is technically possible but typically not what a mall wants. Vintique defaults storewide to mall-bourn; you can change this per-event if your business logic differs.

• Stacking order ambiguity. If your system applies storewide-first-then-vendor, the math comes out differently than vendor-first-then-storewide on the same ticket. Vintique applies vendor first, then storewide, consistently — documented and shown on every receipt.

For more on the operator workflow around event weekends, see

.