Setup guide
From nothing to your first approved change
Seven steps, about twenty minutes. Half of that is the review you do yourself, and that is the part we do not want you to rush.
This guide is public on purpose. Better to see exactly what is needed now than to discover it after opening an account.
Your WooCommerce keys
4 minutesPricebreeze talks to your store through a pair of keys. You never hand over your WordPress password, and you can revoke them any time, from WordPress or from us.
- 1In WordPress: WooCommerce, then Settings, then Advanced.
- 2Open the REST API sub-section.
- 3Click Add key and give it a description, for example Pricebreeze.
- 4Under Permissions choose Read/Write. This is the step people forget most often.
- 5Copy the Consumer key and the Consumer secret. The secret is shown only once.
Why Read/Write and not read only: with read only, Pricebreeze reads your catalogue and shows you everything, but cannot send the changes you approve. The key covers products only. Orders and customers are never requested.
With Read only, the connection succeeds but no approved change ever reaches your store.
Copy both now. WordPress will not show the secret again. If you lose it, delete the key and create a new one.
Connect your store
2 minutesIn Pricebreeze, under Stores, paste your store address and the two keys. The address is the one your customer sees, with https.
Keys are encrypted at the application layer, above the database encryption. Disconnecting deletes them from us. It is good practice to delete them in WordPress too.
Sync your catalogue
3 minutes, in the backgroundWe pull a copy of your catalogue: codes, names, prices, stock status, variations. Without it there is nothing for a price list to match against.
The sync is read only. It changes absolutely nothing in your store. You can leave the page, it carries on by itself, and you rerun it whenever you add products.
Supplier and pricing rule
2 minutesThe rule says how a retail price follows from a wholesale cost: cost times a multiplier, or a target margin. You can add rounding to .90 or .99.
It is a suggestion, not a command. You see it on every row during review and change it wherever you want. With no rule set, the column stays empty and you set the prices yourself.
Example: a wholesale cost of 3.55 € gives a suggested retail of 7.90 €
Your first price list
1 minuteUpload the file exactly as it arrived: a text or scanned PDF, Excel or CSV, up to 20 MB. No cleaning, converting or reordering columns.
Reading runs in the background and tells you roughly how long is left. You can close the page, it resumes from the same point.
The review
5 minutes, or as long as you likeThis is where most of your time goes, and rightly so. Rows are split into five zones, with the ones needing your judgement always first.
Select one at a time or in bulk. Flagged rows are never swept up by Accept all: if something needs a decision, it asks for it separately.
- 11
Needs attention
sharp swings, ambiguous prices, suspicious content
- 186
Ready
matched cleanly and carry a suggested price
- 9
New products
in the price list, not in your store
- 4
Not in price list
matched before, missing from this file
- 0
Skipped
the ones you deliberately left out
Push and undo
1 minuteThe button states how many changes will be sent. Before writing, the system re-reads your store and excludes anything that is not as you saw it. After writing, it reads back to confirm.
Undo covers the whole push and is available from your history. It recalculates nothing: it writes back the prices stored beforehand.
Before you write to us
The five snags we actually see
Almost every connection problem is one of these.
- I lost the Consumer secret
- It does not come back. Delete the key in WordPress and create a new one. Nothing is lost: your Pricebreeze data does not depend on the key.
- It connected, but no change reaches the store
- Almost always the key was created with Read permissions instead of Read/Write. Create a new key with the right permissions and update it under Stores.
- The connection fails with no clear reason
- Check that the address is exactly the one your customer sees, with https and no trailing slash. If the store sits behind a firewall or a coming-soon page, the REST API may be closed.
- It cannot find an EAN field
- That is fine. Matching works on SKU and on product name. If your store keeps barcodes in a custom field, you pick it when connecting and matching becomes even more certain.
- Products with variations get confused
- The sync pulls variations too. When a price list carries the same code on a parent and a variation, the variation wins. If one row would change several variations at once, you are told before you approve.
Twenty minutes, and the next price list takes five
The second time is much faster: the file layout, the matches and the rule are already stored.