Merchant downloads on a product data pool¶
From version 3.8.3
This page describes behaviour available from client version 3.8.3. Sites on an earlier version do not have it yet.
On a product data pool, merchants and buying groups take the product data they have access to. Three things help them keep their own systems up to date: downloading only what changed, keeping their own product codes against pool products, and having their downloads sent to them on a schedule.
Only what changed¶
The product search has a Changed since filter for merchants and groups:
- Our last download shows only the products published or republished since the organisation last downloaded product data on screen. The date of that download is shown in the list.
- A date shows only what was published since that date.
The list and a download use the same filter, so a download with Our last download chosen gives just the changes. A product counts as changed when its supplier publishes it again, whatever was changed.
Your own product codes¶
An organisation can keep its own code against a pool product, for example the code it uses in its own system. The codes are private: no supplier, other organisation or pool staff screen shows them.
- On a product's page, Your code shows the code; users with the edit role add or change it there.
- On the Access page, the Your product codes tab lists every code. Upload codes takes an Excel or CSV file with a heading row: a column Your code, and a column Pool product id, GTIN, or Supplier part number (with Supplier). An empty code removes it. The answer says how many codes were set and which rows were not taken, and why. Download your codes gives them back in the same layout.
- A code is used for one product only, within the organisation.
The code comes back in every download as an extra column Your Product
Code, in full files and scheduled exports, and through the
pool API as memberCode. A system can also find a product
by its own code, and set codes through the API.
A product the organisation can no longer see keeps its code, but the list shows no details for it and downloads leave it out. If access comes back, so does the code.
Scheduled exports¶
An organisation can have a download made on a schedule and sent to it. The Scheduled exports tab on the Access page lists them. Users with the edit role (and pool staff, for any organisation) add and change them. Scheduled exports only work once they are switched on in the pool's settings.
A scheduled export has:
- an export template (the same ones the product search download uses) and, if wanted, one supplier;
- Everything, or Only what changed since the last file;
- when: every day, every week on a chosen day, or every month on a chosen day (1 to 28), at a chosen hour;
- where it goes: by email (up to 10 addresses), to an SFTP server (with a password or a private key), or to an Amazon S3 bucket.
The file is made with the organisation's access and its own product codes, the same as a download on screen. Run now starts one within a minute. Send test sends a small test file to check the address and the password. Files lists the files of the last 7 days, which can be downloaded while they are kept.
- A file too large to email is not attached; the email says where to download it.
- If a file cannot be delivered, it is tried again every minute, 5 times. Then the export shows the failure and the organisation's users are told.
- Passwords, private keys and S3 secret keys are stored encrypted and never shown again. Leaving the box empty when changing an export keeps the stored one.
- For SFTP, giving the server's host key fingerprint is recommended: the file is then only sent to that server.
- For S3, use a key that can only put files into that bucket.