A practical workflow
Follow the guide step by step
- 01
Read a supported public listing
Open the Amazon or Walmart product page and run the visible-page reader when you are ready to audit it. The app uses supported details shown on that page; it does not log in to seller accounts or fetch listings in the background.
- 02
Verify product identity and variation
Match the supplier's product, condition, variant, and sellable quantity to the marketplace listing. Resolve a mismatch before comparing supplier cost with listing revenue.
- 03
Normalize the supplier pack and MOQ
Convert supplier pack cost to the listing-pack basis only after checking pack counts and variation. Confirm the supplier minimum order quantity and the cash required for the full order.
- 04
Select marketplace and fulfillment assumptions
Choose the marketplace and fulfillment method that match the planned operation. Check category, packaged dimensions, shipping weight, eligibility, and current fee assumptions; verify missing or unsupported values.
- 05
Review the full unit estimate
Enter supplier and inbound costs plus applicable advertising, storage, returns, and discount assumptions. Compare estimated profit, margin, ROI, break-even price, and maximum buy price against your own thresholds.
- 06
Stress-test price and inventory risk
Compare the base case with available lower-price scenarios and seller-entered competition or ad assumptions. Enter a monthly sales estimate and planned quantity to review months of cover and cash tied up.
- 07
Resolve blockers and preserve the decision
Check eligibility, hazmat, intellectual-property, pack-match, and fee-confidence diagnostics. Save the audit and its fee-assumption snapshot after verification; use Review rather than Buy when a material check is incomplete.
Keep observed facts separate from seller assumptions
A visible price, product title, or package detail is not the same as a verified supplier match, current marketplace charge, or demand forecast. Keep track of which inputs came from the listing, which came from a supplier quote, which you entered as an estimate, and which still need confirmation.
This order uses the app's product-specific safeguards: the local visible-page read supports listing review, pack matching is required before a Buy outcome, and demand and downside scenarios remain seller-entered planning inputs.
A Buy signal is not an order instruction
Buy, Review, or Avoid summarizes the configured thresholds and current audit assumptions. It does not confirm that the item is compliant, eligible, in stock, correctly represented by the supplier, or likely to sell at the entered price.
Use the saved audit and its dated fee assumptions to document what you checked. Before placing an order, verify current charges and supplier terms and make sure MOQ cash, expected inventory time, and available capital fit your operation.
Make it repeatable
Use the same sequence on every product so decisions are consistent: verify the listing, enter costs, review the audit, stress-test, and set the ceiling.
Save each audit so you can compare your estimate with the real result later and improve your assumptions.
Use a verification gate before the Buy result
The workflow is deliberately sequential: a visible-page reader gathers supported public listing details, the seller verifies identity and variation, supplier pack counts are normalized, and the pack-match check is resolved before the audit can issue Buy. A good margin estimate cannot compensate for comparing different products or units.
After the listing and costs match, review marketplace-specific fees, stress-test available price scenarios, and enter a conservative monthly sales estimate. Check months of cover and MOQ cash alongside unit profit, then save the audit with its dated fee assumptions so the decision can be revisited without silently replacing the original inputs.
- Confirm eligibility, hazmat, intellectual-property, category, and package details independently.
- Use seller-entered demand as a planning scenario, not an app-provided sales forecast.
- Keep Buy, Review, and Avoid tied to the current inputs and configured thresholds.
Common questions
Frequently asked questions
Does the workflow automatically research marketplace listings?
No. You open a supported public listing and run the visible-page reader. The app does not sign in to seller accounts or fetch listing data in the background.
When should an audit remain at Review?
Use Review when product identity, pack mapping, fee-driving measurements, category, eligibility, or another material assumption still needs verification.
Does a Buy result predict demand or guarantee profit?
No. The result uses the current product and seller-entered assumptions. Demand is entered by you, and actual fees, sales, returns, supplier terms, and prices can differ.
What is the right order for sourcing checks?
Verify match first, then costs, then profit, then stress tests, then buy quantity.
Ready to check a listing?
Put the assumptions to work.
Bring the visible listing facts and your own costs into a product audit before you commit to inventory.