Bookkeeping errors: fix sales that didn't save
Learn how to find out why a sale might be missing from Bookkeeping and fix each message.
On this page
- Key points
- Before you start
- "Please log in to DropFlow first" / "❌ Please login to DropFlow first"
- "Insufficient credits — purchase more to record this sale" / "❌ Insufficient credits. Please purchase more credits."
- "Could not save to bookkeeping: …" / "❌ Failed to save: …"
- "Queued locally for retry (N pending)"
- "Auto-bookkeeping is off — saved locally (N pending)"
- "Could not read Amazon order: …"
- "Order does not match a DropFlow Auto Order — skipping"
- "Skipped bookkeeping — this Auto Order was abandoned. Re-run it from the eBay panel."
- "Could not find the order number on this Order History page"
- A sale is missing and I saw no message
- Related articles
Use Ctrl+F (Cmd+F on Mac) to find the exact message you see on the supplier or Poshmark page.
Key points
- Sales are saved from the supplier's order page. If that page didn't load fully, the sale may not be recorded.
- Sign-in matters. You must be signed in to the extension when the sale is saved.
- Some failures are kept in this browser. Messages that say "saved locally" or "queued" mean the sale was not sent yet.
Before you start
- Sign in to the extension.
- Make sure Auto Bookkeeping is on in Auto Order Settings (eBay).
- Check that you're signed in to the supplier account that placed the order.
"Please log in to DropFlow first" / "❌ Please login to DropFlow first"
Cause: You weren't signed in to the extension when the sale was saved.
Fix:
- Open the popup and sign in.
- Reopen the supplier's order details page (eBay sales) or Amazon Order History (Poshmark sales).
"Insufficient credits — purchase more to record this sale" / "❌ Insufficient credits. Please purchase more credits."
Cause: Saving a sale doesn't use credits, so this message shouldn't stop Bookkeeping.
Fix: Reopen the order page and try again. If the message comes back, email contact@dropflowlister.com with a screenshot and the order number.
"Could not save to bookkeeping: …" / "❌ Failed to save: …"
Cause: The server didn't accept the sale. The text after the colon gives the reason.
Fix: Wait a minute and reopen the order page. If it still fails, contact support with the message.
"Queued locally for retry (N pending)"
Cause: The sale couldn't be sent, so it was kept in this browser.
Fix: Check your sign-in and connection, then save the sale again by reopening the supplier's order details page. Failed saves aren't sent again on their own.
"Auto-bookkeeping is off — saved locally (N pending)"
Cause: Auto Bookkeeping was off for this order, so the sale wasn't sent.
Fix: Turn on Auto Bookkeeping in Auto Order Settings, then reopen the supplier's order details page to save the sale again.
"Could not read Amazon order: …"
Cause: The Amazon order details page didn't show the order the way the tool expected.
Fix: Refresh the Amazon order details page. Make sure you're signed in to the account that placed the order.
"Order does not match a DropFlow Auto Order — skipping"
Cause: You opened an Amazon order that wasn't started with Auto Order, so it isn't recorded.
Fix: No action needed. Only orders started with Place Auto Order are recorded.
"Skipped bookkeeping — this Auto Order was abandoned. Re-run it from the eBay panel."
Cause: The Auto Order was started but not finished, so the tool didn't record it.
Fix: Go back to the eBay order and click Place Auto Order again.
"Could not find the order number on this Order History page"
Cause: Amazon Order History didn't show the new Poshmark order yet.
Fix: Wait a minute, then refresh Order History.
A sale is missing and I saw no message
Cause: The supplier tab may have closed before the order page loaded, or the order was placed outside Auto Order.
Fix: Reopen the supplier's order details page while signed in to save the sale again. Sales can't be added by hand.
Related articles
Still stuck? Chat with us.
Email contact@dropflowlister.com with the marketplace order number, the supplier order number, a screenshot, the time, and your extension version.
