Managing deals
Creating, repricing and closing deals, and what each action posts to Discord.
Creating a deal
Deals → New deal. What matters:
| Field | Notes |
|---|---|
| Name | What resellers see. Include the variant — colour, capacity, bundle. |
| UPC | The identity of the deal. Everything downstream matches on this. |
| Price | What we pay per unit. |
| MSRP | Retail reference, used to show margin. |
| Warehouses | Which sites accept it. A deal with none is undeliverable. |
| Product image | Paste, drop or click. Large images are resized automatically. |
| Secondary UPCs | Other barcodes for the same product, so a variant still matches. |
| Active | Only active deals appear to resellers, and only an active deal posts to Discord. |
Creating an active deal posts it to the deals webhook with the product, payout, retail and margin.
Repricing
Changing the price writes a price-history entry with a timestamp, and posts a price-update to Discord showing the old and new figures.
Price history is what pays people
Resellers are paid the price recorded for the moment their goods were checked in, not today's. That lookup reads price history, so every change must go through the deal editor rather than the database.
Closing
Set a deal inactive. It disappears from the catalogue. Existing commitments stop being sendable, and goods already in transit are still honoured at the price recorded at check-in.
Reposting
Repost pushes an existing deal to Discord again, unchanged. Useful when a deal was posted during a quiet hour.