Skip to content

Access to 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.

A pool is a site where many suppliers publish product data and merchants and buying groups take it. On a pool, a supplier decides who sees their data. Other sites are not affected: there, every group user sees every supplier as before.

eBiz switches a site into pool mode in Site Settings → PIM → PIM Mode ("Product data pool") and presses Save Settings. Only eBiz staff see the choice; anyone else sees which mode the site is in, and a save by anyone else keeps the stored mode. The switch is on the PIM tab when the site runs version 3.8.3, and pool features need the PIM on 3.8.3 as well. The Access page (menu: Prices & Products → Access, address /pim/access) then appears for everyone on the site.

Who is who

  • Suppliers work on their own products, as on any site.
  • Pool staff (the site's superusers, users of the site's own company, and eBiz) see every supplier and can act for any of them.
  • Merchants and buying groups are the member companies. They are called parties. A party sees a supplier's products only through access, and never changes them. Without access a party cannot see the supplier's products, files, figures or even how many products there are.

Approving organisations

Pool staff approve each organisation on the Organisations tab, and say whether it is a merchant or a buying group. Only approved parties get access, and suspending a party stops all of its access at once.

A supplier's settings

On the Access tab a supplier (a user with the edit role) chooses a default:

Default Who sees the products
Named parties only Only the organisations named below. This is the default.
Members of chosen buying groups The chosen groups and every merchant in them, plus anyone named
All approved merchants and groups Every approved party

Prices can be included with the default or left out.

Named access adds organisations one by one. Each grant can be limited:

  • to some ranges and brands (none ticked means all);
  • by leaving out parts of the record, the sections of the product template;
  • with or without prices. Prices are left out unless the grant says otherwise.

A grant to a buying group can extend to its members. The group keeps its own member list on its Members tab.

Where a party has access in more than one way, it sees everything any of them opens. A part of the record is left out only when every way in leaves it out.

Withdrawing access takes effect at once. The grant stays in the list, marked withdrawn.

Asking for access

A party's Suppliers tab lists every supplier on the pool with the party's access: none, asked, or granted (and whether limited). Ask for access sends the supplier a request with an optional message, and the supplier is notified. The supplier approves it, choosing the limits as for a grant, or declines it with an optional reply, and the party is notified. A party can withdraw a request it has not had an answer to.

The access log

The Access log tab shows, for a period, which organisations used the supplier's data: products found in searches, products opened, rows downloaded, rows pulled through the API and files opened, with the number of days and the last time. Counts are kept per day.

What a merchant or group sees

Merchants and groups use the same PIM screens as everyone else. Suppliers they have no access to simply do not appear. The screens are read-only for them: edit buttons, bulk actions, imports and the menu items they cannot use (Updates, the calendar, price comparison, the Price File Tracker and the template editor) are hidden. On a product:

  • the Pricing tab is hidden unless the supplier shares prices;
  • the fields of any section the access leaves out are taken out of the product, in search results, downloads and the API as well as on screen. The product's keys (part numbers, GTIN, name, manufacturer) always stay.

They can download products from search in the template's layout, with the same parts left out.

Publishing

On a pool, what merchants and groups see is what the supplier last published. Suppliers edit and import as on any site, and those changes are their working copy until they publish them.

The Publishing page (/pim/publish) shows how many products are not published, changed since they were published, and published and up to date, with a list of each. A supplier user with the edit role, or pool staff for any supplier, can:

  • Publish selected products, or Publish all changes (every product not published or changed since);
  • Withdraw selected products, so merchants stop seeing them until they are published again.

A note can go with each publish. The publishing record lists every publish and withdrawal: when, by whom, how many products, and the note. A publish or withdrawal that is still running also shows with the site's other running tasks. Each product's history shows when it was published or withdrawn, at which version, and whether staff did it for the supplier.

A product counts as changed when anything about it is saved after it was published, including its prices, Template tab values and linked files. A product that has never been indexed for search is skipped until it is, and the record says how many. Publishing more than 500 products at once runs in the background.

What merchants and groups read comes from the published copy: search, downloads and the API use a separate published search index, and the product screen's Template, ETIM, Packaging and Media tabs show the values as published. A merchant's view of a product's history stops at its last publish. Deleting a product also withdraws it.

The Data Quality page still scores the working copy, for everyone.

Product data on the dashboard

There is no separate workspace or console page. From 3.8.3 the home dashboard starts with a product data block, and what it holds depends on who is signed in.

A supplier sees:

  • four figures: live products (and how many are waiting to be published), the share of products at Data Level 1 or above, the Confidence rating, and documents expired or expiring;
  • To do: access requests waiting for an answer, products not published or changed since publishing, products with data errors, products below Data Level 1, and expired or expiring documents. Each links to the page that deals with it where there is one;
  • Who can see your data: the default, the organisations named, and any asking for access;
  • Used in the last 30 days: how many organisations used the data, and the ones that used it most;
  • Recent imports: the last three import runs.

Pool staff see what needs attention (organisations waiting for approval, access requests waiting, suppliers over their tier limits, rated red, or late on onboarding), suppliers by onboarding stage, and suppliers by Data Level. A supplier's Data Level band there is the highest level that at least half of its products reach. Staff see one supplier's block, the same one the supplier sees, on that supplier's company page.

A merchant or buying group sees one link: products changed since their last download, which opens the product search with that filter.

On a site that is not a pool, a supplier sees one compact product data card: live products, the share at Data Level 1 or above, documents expired or expiring, and the date of the last import.

The Confidence rating

Each supplier is rated green, amber or red by how long ago they last confirmed their data: by pressing Confirm data is current on their dashboard (no re-upload needed, and a note can go with it), by publishing, or by loading data. By default a supplier is green for 90 days, amber until 180 days, then red; a supplier that has never confirmed is red. A linked document past its expiry date holds the rating at amber. Data Yard sets these periods, and whether an expired document makes the rating amber, red or does not count, under Confidence rating on Site Settings > PIM.

The rating shows on the supplier's dashboard, where anything but green is on the to-do list, and in a Confidence column on the Data Quality page's Suppliers tab, with the reason when you point at it.

Subscription tiers

Data Yard can give each supplier a tier with limits. Tiers are set under Supplier tiers on Site Settings > PIM: each has a name, a product limit, a user limit (0 means no limit) and the features it includes (product media, loading filled-in templates, ETIM classification). One tier can be the default for suppliers not given one. With no tiers set, nothing is limited.

The Tiers view on the Onboarding page lists every supplier's tier and its use of it, and is where staff change a supplier's tier. A supplier over its limits is marked.

  • A product limit stops imports creating products past it: the rows beyond are not created and the import report says why. Existing products are still updated.
  • A user limit is reported, not enforced, because users are added through the contact screens.
  • A feature not in the tier is refused when the supplier, or staff for them, tries to use it.

Onboarding suppliers

Pool staff follow each supplier from signing to merchants seeing their data on the Onboarding page (/pim/onboarding). Each supplier is at one of six stages: Signed, Data received, Structured, Validated, Published and Access granted. Each has an owner from the pool's own staff, a target date and notes.

The board has a column per stage; List shows the same as a table. Each card shows the supplier, its owner's picture, the target date (in red when it has passed), the number of notes and products, and the latest note. Drag a card to another column to move the supplier to that stage, or use the arrows on the card. Above the board the page says how many suppliers are not being tracked yet; Track a supplier opens a finder, where typing part of a name lists the matching suppliers and clicking one puts it on the board at the first stage.

Beside each supplier the platform shows its own evidence: products loaded, products with template data, products at Data Level 1 or above, published products, and whether anyone has access. When the evidence is ahead of the recorded stage, the card asks Ready for …?; moving a supplier on is always a person's decision. Moving to a stage records the date it was reached, and every move is added to the notes. A supplier can be archived off the board.

On a site that is not a pool

The Onboarding page is not limited to pools. On any other site it is there for the site's own staff (eBiz, the site's superusers, and users in the site's own company), with the first four stages only: Signed, Data received, Structured and Validated. Published and Access granted belong to a pool and are not offered. Cards show products at Data Level 1 or above in place of published products, the Tiers and Report views are not shown, and once any supplier is being tracked the staff's home dashboard shows suppliers by stage.

The evidence figures are refreshed at most every five minutes.

What moves by itself

A stage marked Automatic takes a supplier by itself once its evidence is met. With the standard stages that is Data received, Structured and Validated; Published and Access granted on a pool are suggested (Ready for …) but left for a person to move, unless the site ticks them.

  • A supplier on the board is moved to the furthest automatic stage whose evidence is met. It is only ever moved forward: if the evidence later goes, or a person has put the supplier ahead of the evidence, the card says Evidence not met and stays where it is.
  • A supplier with products that is not on the board is put on it at that stage. Suppliers with no products stay off the board until someone adds them with Track a supplier. This can be switched off in the settings.
  • Archived suppliers are left alone.
  • Every automatic move is added to the supplier's notes with what was met, for example "Moved automatically from Data received to Validated: half the products are at Data Level 1 or above".

The platform looks when the board is opened (at most every five minutes), and, on a site that already has suppliers on the board, after each Data Quality build and each product import. A message on the board says how many suppliers were added or moved since it was last opened.

Choosing the stages

The stages are set on Site Settings > PIM > Onboarding stages. A site with no list of its own uses the standard stages (the six above on a pool, the first four anywhere else); Start from the standard stages copies them in to be changed. Each stage has:

  • a code, which supplier records and stage dates are kept by, so it is fixed once the stage is saved;
  • a name, which can be changed at any time;
  • optionally the evidence the platform checks before suggesting a supplier is ready for it: products are loaded; products have template data; half the products are at Data Level 1 or above; and, on a pool, products are published, or published with a merchant or group given access. A stage with no evidence is only ever moved by hand.
  • Automatic, for a stage with evidence: whether suppliers are moved to it by themselves once the evidence is met.

Below the list, Put a supplier on the board by itself once it has products is ticked unless the site switches it off.

The arrows change the order. The last stage is the finish: a supplier past its target date and not yet there is late. A stage that suppliers are at (the count is shown beside it) cannot be removed, and the settings are not saved if the list leaves one out; move those suppliers to another stage first. Onboarding needs at least two stages.

Organisations' own users

Merchants, groups and suppliers look after their own people through company self-management: their managers ask for people to be added, changed or removed, and a superuser signs off each change. Data Yard approves new organisations on the Organisations tab of the Access page.

The pool report

The Report view of the Onboarding page shows use by organisation over the last 90 days and growth by month over the last 12. Download for the board gives those, with the pool's headline figures, as an Excel workbook.

Staff acting for a supplier

Pool staff can do everything a supplier can, for any supplier: edit and import products, publish and withdraw, and set access. Each product's history shows who made a change and marks it on behalf of the supplier, including publishing and withdrawing.

Where access is checked

On the server, for every party: product search and its filters, the product screen and its Template, ETIM, Packaging and Media tabs, change history, spreadsheet downloads, the PIM API, asset files, the supplier lists and the Data Quality page.

The Data Quality page shows a party only the suppliers whose whole catalogue it can see, because its figures are not split by range or brand.

The Price File Tracker, category management teams and the indexing tools are not open to merchants and groups on a pool at all: they compare suppliers' prices or are for staff.