RestocksAIO
Home/Blog/Daily operations: keep owned stock, listings, payouts and documents in agreement
Multi-platform selling

Daily operations: keep owned stock, listings, payouts and documents in agreement

Listing count is not stock. One owned unit can have several linked marketplace listings on purpose. Each day, reconcile confirmed unfulfilled sales against owned units, then close payouts and paperwork without putting a sold unit back on the shelf.

What must stay in agreement

Treat owned units as the source of truth. Live asks, listing count and the sum of marketplace quantities are not committed or sold quantity. A sale is only a stock event after it is confirmed and unfulfilled. Completing payout, invoices or fulfilment never makes that unit available again. Restore availability only after a confirmed cancellation or a physically received and checked return.

Automation can load pending sales, keep linked listings grouped, and generate documents from sale data. Manual checks still own physical counts, return inspection and any marketplace screen that the software does not write. Do not delist valid cross-listings merely because offers exceed stock. For the listing model, see how to avoid overselling when you list on five marketplaces.

Daily reconciliation checklist

Run this ordered list once per operating day. Each step names the input, what to check and what to do with the result.

  1. Owned units vs confirmed unfulfilled sales. Input: inventory quantity plus the day’s confirmed, not-yet-shipped sales. Check that remaining available units equal owned minus those sales. If a unit is short, stop listing and fulfilment on that SKU/size until the physical count matches. If a unit is long, do not add availability until you find a missed cancellation or a received return.
  2. Sibling-listing cleanup after a sale. Input: the sold owned unit and its linked listings. Check that remaining live listings still describe leftover owned units, not the sold one. If a sibling listing is still live for a unit you no longer own, remove or pause that listing. Leave other valid cross-listings in place.
  3. Paid vs pending payouts. Input: Account Sales from platforms and Inventory Sales from your stock. Check which sales are marked paid and which are pending. Use pending as a cash-flow signal only; never treat a pending payout as a reason to restock the sold unit.
  4. Sale-linked documents. Input: confirmed sales with carrier and business-profile data. Check invoices, labels and proof of delivery against the same sale record. Generate missing invoices from eligible paid sales, generate labels from confirmed sales, then pull POD after the supported shipping steps. Archive documents next to the sale; do not rebuild them from a blank template.

Manual checks versus automation

Use monitors and confirm-sales workflows to load pending marketplace sales and, where you enable them, auto-confirm. Use grouped inventory views to see linked listings. Use sales and payout tracking to mark paid versus pending. Use invoice, label and pickup/POD tools only on the sale they belong to.

Keep humans on: counting boxes, inspecting returns before restoring quantity, confirming a cancellation in the marketplace UI when the feed is unclear, and refusing to treat listing count as stock. If a return arrives, check the physical item first, then restore availability. If a cancellation is confirmed, restore only that unit—not a generic quantity bump.

Exception queue: cancellations, returns and unmatched sales

After the daily count, work only the exceptions. Completing payout or paperwork never restores a sold unit. Restore availability only after a confirmed cancellation or a physically received and checked return.

  1. Unmatched confirmed sales. Input: confirmed unfulfilled sales that do not map to an owned unit. Check SKU, size and sale id against inventory. If the unit is missing, stop listing and fulfilment on that size until the physical count matches. Do not invent quantity from listing count.
  2. Cancellations. Input: marketplace cancellation status plus the owned-unit record. Check that the cancellation is confirmed in the seller UI when the feed is unclear (manual). Then restore only that unit. Leave other linked listings in place if leftover owned units remain.
  3. Returns. Input: inbound parcel and the original sale. Check the physical item first. If it matches the sale and is sellable, restore availability and re-link eligible listings. If it does not match or is damaged, keep quantity at zero for that unit and keep documents on the original sale.
  4. Sibling listings still live for a sold unit. Input: the sold unit and its grouped listings. Check remaining live asks describe leftover owned units only. Pause or remove listings for units you no longer own. Do not delist valid cross-listings merely because offers exceed stock. See how to avoid overselling when you list on five marketplaces.

Automation can load pending sales, group linked listings and mark paid versus pending. Manual checks own box counts, return inspection and any marketplace screen the software does not write.

End-of-day close without treating listings as stock

Close the day on the sale record, not on a tab count. Paid versus pending is a cash-flow signal only.

  1. Payout split. Input: Account Sales from platforms and Inventory Sales from your stock. Check which rows are paid and which are pending. Leave pending open; never restock from a pending payout. For the bookkeeping view, see bookkeeping for high-volume sneaker resellers.
  2. Sale-linked documents. Input: confirmed sales with carrier and business-profile data. Check invoices against eligible paid sales, labels against confirmed sales, and proof of delivery after supported shipping steps. Generate missing documents from that sale; archive them next to it. Do not rebuild from a blank template. Related: invoices from sale data and labels and proof of delivery.
  3. Open fulfilment. Input: confirmed unfulfilled sales still without a label or pickup. Check each still maps to an owned unit you counted today. Queue labels and pickups on those sales only. A missing document is not a reason to add stock.

Leave tomorrow a short exception list: unmatched sales, uninspected returns, unpaid rows and documents still missing on a sale. That is the operating close—not a listing-count screenshot.

Reconcile each owned unit with its listings

Start with the physical pair and its inventory record, not the number of live listings. A single owned unit may have several linked marketplace listings; those listings do not add stock.

Use this ordered checklist when a sale appears. The input is the sale record and the unit it may match. Check each result before you change availability.

  1. Match the sale to a unit. Input: the marketplace sale ID, style code, size and your inventory record. Check that the pair physically exists and that the sale is confirmed and unfulfilled. Match it to one owned unit; if details do not line up, record the mismatch and hold changes until you resolve it.
  2. Check other linked listings. Input: the matched unit and its marketplace listings. Check whether a listing still offers that same sold unit. If it does, verify cleanup in the marketplace. Leave valid listings for other owned units in place; do not remove them just because one pair has several listings.
  3. Update availability only on evidence. Input: the confirmed sale, a confirmed cancellation, or a return parcel. Keep a sold unit unavailable. Restore it only after the marketplace confirms cancellation, or after you physically receive and inspect the return. Record the result against that unit.

Automation can load pending sales and group linked listings where supported. The physical count, ambiguous sale match and return inspection are manual checks. For the related workflow, see how to avoid overselling across marketplaces.

Close payout and document records against the sale

Use the sale record as the link between stock, payout and paperwork. A paid payout, invoice, shipment or delivery proof does not make a sold unit available again.

  1. Compare sale and payout records. Input: marketplace sale details and the payout details you can access. Check the sale reference, amount and whether payment is marked paid or pending. Mark a match only when the records agree; otherwise keep it on a manual exception list with the missing detail.
  2. Check documents against the same sale. Input: the confirmed sale and any invoice, label or delivery proof. Check that each document belongs to that sale, then generate or retrieve missing documents using the supported workflow. Keep the documents with the sale record rather than starting a separate, unlinked file trail.
  3. Review open exceptions. Input: unmatched payouts, missing documents and unresolved sale-to-unit matches. Write down the sale ID, what does not match and the next check. Keep the unit unavailable if its sale or ownership is still unclear.

Sales and payout tools can show paid and pending records; document tools can create supported invoices and labels or retrieve proof of delivery. You still compare unmatched details by hand. See how to match payouts to sales and investigate gaps.

Add restock.gg as a preferred source on Google

Related reading

All articles

Ready to run it like an operation?

7-day Standard trial, or a 3-day Premium setup sprint. Pricing, inventory, listings, documents and analytics in one pane.