To automate an eBay sold-item log into per-item profit, join your eBay sales export to a cost-basis table on a shared SKU, then let formulas subtract fees, postage, and cost from each sale. The log needs 11 fields. Without a SKU and a cost basis on every row, no spreadsheet can calculate profit for you.
Most resellers start with the eBay sales report and call it a log. It tells you what sold and what eBay paid out. It does not know what you paid for the jacket. This post covers the fields that close that gap, a build you can finish in an afternoon, and the volume where a spreadsheet starts costing you more than it saves.
Why the eBay export alone can't show per-item profit
Take a sale of a wool overcoat at $64.00. The export shows the sale price, the final value fee, and the payout. It does not show the $9.50 you paid at the thrift store, the $1.10 you spent on a poly mailer and label supplies, or the fact that it sat in bin C4 for 71 days. Those live in your head, a notebook, or a receipt pile.
That is the failure mode: revenue is tracked, cost is guessed. A reseller doing 150 sales a month who guesses cost by 10 percent in the wrong direction misreads profit by hundreds of dollars. The fix is not a fancier report. It is a log where every sold row can find its own cost.
The 11 fields a sold-item log needs
These are the fields that let formulas do the work. Split them by where they come from.
| Field | Source | Why it matters |
|---|---|---|
| SKU | Your inventory sheet (matches eBay Custom Label) | The join key between sale and cost |
| Order number | eBay export | Prevents duplicate rows on re-import |
| Sold date | eBay export | Monthly and quarterly cuts |
| Sale price (item) | eBay export | Revenue line |
| Shipping charged to buyer | eBay export | Revenue offset against postage |
| Final value fee + per-order fee | eBay export or transaction report | Largest cost after COGS |
| Ad fee (Promoted Listings) | eBay export | Often missing from simple profit math |
| Postage paid (label cost) | eBay export or carrier | Varies by weight and zone |
| Cost basis | Inventory sheet | What you paid, including allocated costs |
| Supplies cost | Flat rate per item | Mailer, tape, labels |
| Refund amount | eBay export or manual entry | Partial refunds and returns |
Add one optional field if you grade: the condition tier at listing time (NWT, NWOT, Excellent, Very Good, Good, Fair, or Poor). It lets you see profit by tier later, and it makes a not-as-described refund easier to trace back to a grade call.
How to build the log in 8 steps
This is the minimum build in Google Sheets or Excel. Plan on two to three hours the first time.
- Create an inventory tab with one row per item: SKU, purchase date, source, cost basis, bin location, and listing date. Give every item a unique SKU before it is listed.
- Put the SKU in the eBay Custom Label field on every listing, so it flows into your sales export.
- Download the eBay Orders report from Seller Hub for a date range, as a CSV. Download the transaction report too if your orders file lacks fee detail.
- Create a raw-import tab and paste the CSV in unchanged. Never edit this tab by hand.
- Create the sold log tab. Pull order number, date, SKU, sale price, shipping charged, fees, and postage from the raw tab.
- Add lookup columns. Use XLOOKUP or INDEX/MATCH on SKU to pull cost basis from the inventory tab, then add a flat supplies cost.
- Add the profit formula: sale price + shipping charged - fees - ad fee - postage - cost basis - supplies - refunds. Add a margin column: profit divided by sale price.
- Add a check column that flags any row where SKU is blank, cost basis returns an error, or the order number already exists. Fix flags before you read any totals.
[Mockup: sold log tab with the check column highlighting two rows with missing SKUs]
What the math looks like on real rows
Here are three example rows. The numbers are illustrative, but the structure is exactly what your sheet should produce.
| Item | Sale + shipping charged | Fees + ads | Postage | Cost + supplies | Profit |
|---|---|---|---|---|---|
| Wool overcoat | $64.00 + $0.00 | $9.00 | $14.20 | $9.50 + $1.10 | $30.20 |
| Raw denim jeans | $48.00 + $8.00 | $7.40 | $8.10 | $6.00 + $0.90 | $33.60 |
| Fleece pullover | $22.00 + $0.00 | $3.30 | $6.90 | $4.00 + $0.90 | $6.90 |
The fleece looks fine at $22.00 and lands at $6.90 profit, a 31 percent margin. If it had come back with a partial refund of $5.00 for a pilling complaint, profit would drop to $1.90. A log that carries a refund column shows that instantly. A payout total does not.
Where a manual log stops scaling
A pasted-CSV log works well at low volume. It breaks at predictable points, and you can measure them.
- Time per import. If pasting, cleaning, and checking a week of orders takes 20 minutes, that is fine at 40 sales a week. At 200 sales a week with returns, it becomes an hour or more of work you do not get paid for.
- Check-column flags. If more than about 3 to 5 percent of rows get flagged each import, your SKU discipline is leaking faster than you can patch it.
- Partial refunds and returns. Each one needs a manual edit to the original row. Once you handle several a week, errors creep in.
- Multiple platforms. The moment Poshmark, Mercari, or Whatnot sales join the log, every platform has a different export format, fee structure, and payout timing.
- Multiple people. Two people editing one sheet means broken formulas and overwritten cost cells sooner or later.
A rough rule: when you pass about 300 items a month, or when log upkeep takes more than 90 minutes a week, the spreadsheet is costing you listing time. Treat that as a guideline, not a law. A seller with simple items and clean SKUs can stay on a sheet longer. A seller with heavy returns should move sooner.
What to automate first, and what to keep manual
You do not have to automate everything at once. Rank by how often the task repeats and how costly mistakes are.
- SKU assignment at intake. Mistakes here corrupt every downstream number.
- Order import on a schedule instead of a manual CSV paste.
- Cost basis lookup by SKU, with no retyping.
- Fee, ad fee, and postage capture per order.
- Refund and return adjustments linked to the original sale.
- Payout matching, so each deposit ties to the orders inside it.
Keep judgment calls manual: whether to write down aged stock, how to split a bundle's cost across items, and whether a refund was fair. Software should deliver the numbers. You make the decisions.
One tie-in worth tracking: returns flagged as not as described show up as a refund line in your log. If you record the condition tier on each listing, you can see whether Good and Fair items return more often than Excellent or Very Good ones, and whether the cause is Fabric Condition, Cosmetic Appearance, or something else. That turns a vague return rate into a specific fix.
Try it on one week of sales
Build the sheet above with last week's orders and see how many rows pass the check column on the first try. If most do, keep the spreadsheet and tighten your SKU habit. If you spend more time fixing rows than reading profit, that is the signal to automate. FlipDesk Reconcile ties each sale, fee, postage charge, and refund to the item's cost basis for you. Run one week of orders through it and compare the result to your sheet.