Observed beats assumed
Answers point to what a dated observation can support.
FAQ · First row
Lovegobuy Spreadsheet First Row FAQ
The answers keep a first row small, dated, and honest about what was actually seen.
Starting questions
- Can the first row be a saved search?
- No. A search is a path, not a row; the first row describes one item from one listing.
- Should I fill every column on day one?
- Fill the columns the listing can support; empty columns with notes beat invented values.
- Is one row too slow?
- The first row teaches the gates; later rows reuse them quickly.
Stop-rule questions
- What stops a save completely?
- A page that redirects to a different item or hides behind a login or challenge screen.
- What only pauses a save?
- A missing price or a missing photo view pauses the row at the evidence gate with a dated note.
- Can I guess a color name?
- No; paraphrased option text breaks the row when the listing changes or the order needs the exact wording.
After-save questions
- When does the first row need a recheck?
- Before any payment step that depends on the row, or when the platform reports the listing changed.
- What if the price moved after saving?
- Add the new observation with its date; the row keeps both values instead of overwriting.
- Where do returns questions go?
- Return terms belong to the platform's own guide pages; the row only links the listing facts you observed.
Gate detail
Gates are habits, not forms
Once the identity, evidence, and date gates feel automatic, the same three checks protect every later row without extra effort.
Gaps stay visible
Unanswered parts of a question stay named instead of papered over.
Decisions stay dated
Every recheck carries the date that makes it retraceable.
Carry unanswered parts into the next live check
A static answer should never disguise a changing platform detail.
For current logistics rules, the Lovegobuy shipping and returns guide is the platform's own reference.
Back to overview