I built an inventory app for resellers where every unit is its own record. Looking for feedback on the approach.
Disclosure up front: I'm the developer. This isn't a sales pitch; I'd really like this sub's take on how I've modeled the inventory side.
Who it's for: resellers who buy stock locally (thrift, pawn, flea, estate, outlet) and resell it online or in person. Spreadsheets break down for them fast. One sourcing trip can mean 30 different items at 30 different costs, and the real cost of each item includes the gas spent getting it.
How it handles inventory (the part I'd like feedback on):
- One row per unit, with no quantity field. If you buy three identical mugs, you get three records. Each one has its own cost, status and sale history. Selling or deleting one never touches the others.
- Landed cost includes gas. You log the miles for a trip. The app works out the gas cost from your MPG and gas price, then spreads it across the items bought on that trip. ROI is shown both with and without gas.
- Refunds add records instead of editing old ones. A refund puts the item back into inventory in the status it had before the sale. The original sale and invoice stay untouched, so the history still adds up.
- An item only becomes sold through a sale record. That's either a full invoice or a quick "mark sold" that creates a minimal invoice. Analytics never counts a sale that has no record behind it.
- Receipt scanning for item costs, and in-person card payments: Tap to Pay on iPhone or a Stripe Bluetooth reader.
Questions for you all:
One record per unit or a quantity field: has one-per-unit caused you trouble at scale, or saved you from it?
How do you allocate shared costs like gas, ? Evenly per unit, or weighted by cost?
What would you expect next: CSV import, marketplace sync, or something else?
It's an iOS app called Sourcerer, with a 7-day free trial and no card needed. If you want to try it:
https://apps.apple.com/us/app/sourcerer-resell
Happy to answer questions about the data model