Skip to main content

Match your product list

This guide describes locally prepared work. Release and live account acceptance have not yet been verified.

Open Your workspace → Match products for your business or an All Access personal workspace. You must be a current member; a separate personal subscription does not give access to someone else's business.

Choose a CSV with no more than 2,000 product rows and 1 MB. Commas, semicolons, quoted commas and line breaks are supported. Give each column a different heading. Select the columns for your product reference and perfume name or text, plus brand, strength and year where available. Other columns stay on your device.

The page shows the row count and monthly call cost before you press Match products. Each checked row uses one call. Lists are checked in batches of 100, in order. If the allowance runs out, later rows remain unchecked. Catalogue service failures are free; a lost response can leave usage uncertain, so check current usage before starting again.

  • Matched: the catalogue's strict matching rule identified the perfume.
  • Check this one: a suggestion, requiring your review. Suggestions remain off until their own Jev calibration passes.
  • No safe match: the catalogue could not safely identify a single perfume.
  • Not checked: the row has no confirmed completed result.

Matching does not approve a product link. The account upload does not save a proposal until you choose Save these for approval. An API key may explicitly request propose_links: true to save proposals with matching; it can never approve them. Download the results as CSV. Candidate perfume IDs are included, and spreadsheet formula-leading values are made safe in the download; the product references held during matching are unchanged.

Each completed batch is retained on this device for the signed-in user and workspace. Reopening the page restores results without sending or charging for rows again. An interrupted last request may still have used calls. If device storage cannot retain results, further batches stop and the page asks you to download the results immediately. Previous jobs are archived locally when a new job replaces them.

See API refusals for invalid_rows, too_many_rows and body_too_large, and the builder for saved looks.

After matching, choose Save these for approval. This saves proposals in your business account without repeating matching or using another matching call. If saving fails, keep the downloaded results and retry the save; do not repeat matching merely to save proposals.

The account shows Ready to approve, Pick one, Not in Sniffopotamus and Linked. Suggested candidates show brand, name, strength and year. Their identity is read from the catalogue when proposals are saved. Members may submit proposals; only a signed-in owner or verified Sniffopotamus administrator may approve, reject or unlink.

Select the products and candidates, choose Approve selected, then confirm Link these products? Each will show its card on your site. Nothing is approved before confirmation. Approval checks the perfume is still public and still a candidate. A perfume joined into another is refused with the surviving ID for review; it is not silently relinked.

New matching preserves an already approved link. A different current suggestion is shown beside it. Unlink archives the saved link and asks for confirmation. Rejected and archived records are retained. If a decision response is lost or refused, refresh the list and check it before retrying; earlier decisions in a large selection may have succeeded.

Saving a proposal can fail after matching has completed. The API retains the checked rows and calls_used, and reports the proposal outcome separately. Use the session save to retry a proposal; matching calls are not refunded or repeated automatically.

See API refusals for person_only and not_a_candidate. The new saved-link surface remains locally prepared until its database change and release are approved and verified.

Back to SniffopotamusReturn to the app