Product sources
Connect the place your products come from, choose how often we read it, and decide what should happen to your products if it ever stops answering.
The sources table
Brand → (your brand) → Products → Sources lists every catalog feeding this brand. Until you add one, the page says No product source yet and offers Add source and How the Product API works.
Once the brand has a source (other than Your website, below), a yellow notice above the table says "Don't teach the same product pages twice": Now that your products come from this feed, make sure the same product pages are not also taught to your AI on the Website list. Those copies don't update as fast and can give old prices and stock. Its Check my website pages link opens the Website group on the Knowledge screen.
| Column | What it tells you |
|---|---|
| Name | The source name. Underneath it shows the type — Shopify or WooCommerce shop, Product feed, Product API or Your website — and the address. A push-only API source shows push only instead of an address. Click the name to edit the source (on a Your website source, it opens the last run report). |
| Status | See the badges below. |
| Refresh | "Every day", "Every 3 days", "Push only", "Stopped after 3 failures", or "At least once a week" for Your website. |
| Last successful fetch or push | The date of the last successful read. A push-only source shows "Pushed …" with the date your shop last sent us changes, instead of "Never". |
| Products | How many base products this source currently holds. Versions are not counted here. When a run left products out, a line under the count says Learned 40 of 100 products. The rest wait for credit. (workspace owners also get an Add credit button) or Learned 40 of 100 products. Choose a plan to learn the rest. See Learning order and the 500-credit line below. |
Status badges
| Badge | Meaning |
|---|---|
| Waiting for first run | Created, but nothing has been read from it yet. A push-only source leaves this state as soon as your shop's first push succeeds. |
| Running | A read or a push is running right now. |
| Active | The last read succeeded. |
| Needs attention | The last attempt failed. We keep retrying every hour. |
| Stopped | Stopped after three failures in a row. |
Hover the information icon beside a badge for the plain-English reason, including the raw error (Reason: …) when there is one.
Adding a source
Press Add source. The window, Add a product source, first asks Choose how Yaplet gets your products. The type can't be changed later. Pick Shopify or WooCommerce shop (the first card, already selected and marked Recommended: your shop's address is all we need), Product API (your shop serves products as JSON and can push changes as they happen) or Product feed (the link to the product feed your shop already has — Google Shopping, Heureka, Árukereső or Ceneo; sizes and colors become versions, but there are no keys), then press Continue. The type is the one thing you cannot change later. The fourth card, Your website, adds no source: it shows the switch that turns your website's product pages into products (see Products from your website below). Not sure? The Open the API tab link shows the JSON a Product API source expects. The second step asks for the fields below, and has Add source and Back buttons.
Fields for every source
https://; a product feed may use plain http. On a shop source type the address any way you like — yourshop.com, or a link to one of its products — and we keep just the shop's own https address. Leave it empty on a Product API source to make it push-only: the schedule switch turns itself off and cannot be switched on, no first read is started, and the source simply waits for your shop to send it products.Extra fields for a Product API source
Signature header on every read, so your shop can check the request really came from Yaplet. The secret itself never travels. When you edit a source, an empty field keeps the current secret — unless you also move the address to another host or give a push-only source its first address; then a new secret is generated, so a stored secret never follows the source to a new server.Signature, Host or Content-Length.Shopify or WooCommerce shop sources
A shop source needs only a name and your shop's address. We read the shop's public product list — the one it shows every visitor — so it works only for a shop that runs on Shopify or WooCommerce and shows its products publicly. For a shop on anything else, or one that keeps its product list closed, use a Product API or Product feed source instead.
A shop source has no shared secret, extra headers, key fields or push address, and nothing can be pushed to it. Like a product feed, it carries no keys, so only instructions set to every product reach its products.
It is read on the schedule you set, like a product feed, and each read takes the shop's whole public product list. A read that fails changes nothing: your products stay as they were. What happens to them after three failures in a row is up to If the source keeps failing.
If your workspace was started with Start free from your Yaplet demo, the demo's product cards come along, so the list is not empty from the first moment. If the demo read your products from a Shopify or WooCommerce shop, the shop may already be in the list as a source, and it then reads the whole shop. Products that came from your website's pages go into the Your website source instead. The cards come along only when there is room for all of them; otherwise the normal read learns what fits.
What it brings in
For every product: its title, link, description, picture, category and brand. For every version of a product — a size, a color, a flavor — its options, price, sale price and stock. A sale price is kept only when it is lower than the regular price. A WooCommerce shop also sends each product's rating and number of reviews, and its place in the shop's sales order, which Yaplet keeps as the product's popularity.
Limits of a shop source
- 20,000 products per source (1,000 for an organization with no subscription and no credit balance). A shop that lists more fails the read.
- 500 versions per product. A product with more keeps its first 500, in the shop's order; the product is not refused.
- 15 minutes per read. A read still running after that stops.
When a shop source cannot be read
The source's row shows what went wrong: hover the information icon beside its status, or open Last run report.
| Message | What it means |
|---|---|
| No public Shopify or WooCommerce product list was found at this address. Use a Product API or CSV source for this shop. | The shop is not on Shopify or WooCommerce, or its product list is not public. Use a Product API source, or a Product feed source, for it instead. |
| The shop's product list is empty. | The shop answered, but lists no products. |
| The shop lists … products; the most one source can hold is … | The shop has more products than one source may hold: 20,000, or 1,000 while nobody is billed. |
| The shop's products come to more than … MB; the most one source can carry is … MB. | All the shop's products together are bigger than the size limit in the tables below. |
| Reading the shop took longer than 15 minutes. | The shop was too slow to read in one go. |
A shop that is too big for its limits — too many products, or too large altogether — counts as a failed read, like any other failure. After three in a row the source is Stopped, but unlike other stops, no email or notification is sent: the reason shows only on the source's row. Fetch now starts it reading again.
Product feed sources
A Product feed source reads the feed link your shop system already has, from the Feed link you give it. It reads these feeds:
- Google Shopping — XML, or CSV with commas, semicolons or tabs between the columns.
- Heureka and Zboží — XML.
- Árukereső and Compari — XML or CSV.
- Ceneo — XML.
Yaplet tells the format by itself, so there is nothing to choose. Feeds saved in older Central European text encodings, such as windows-1250, are read with their accented letters intact. A product feed carries no keys, so only instructions set to every product reach its products. Product and image links inside the feed must be normal http or https links: a row with any other kind of link is skipped, and the run report counts it under Skipped as invalid.
Sizes and colors become versions
Rows that share a group id become one product, with a version for each row. The group id is Google's item_group_id, Heureka's ITEMGROUP_ID or Árukereső's GroupId. Each version gets its options from the feed details that differ between the rows (for example Size: S and Size: M), up to five options. A row with no group id is a product of its own. Your product limit counts products after this grouping, not rows.
Feed details become product facts
The details a feed carries are saved as product facts: Heureka's PARAM entries, Árukereső's attributes, Ceneo's attributes, and Google's color, size, material, pattern, gender and age group columns. They show on the product's Attributes tab, and your AI can quote them in answers. A fact that every version shares belongs to the product; one that differs between versions becomes an option of those versions.
Prices and currency
Yaplet reads only the price a buyer pays, VAT included, and never a price without VAT. When the feed's prices carry no currency, it comes from the country ending of the feed link's address: .hu is HUF, .cz is CZK, .sk is EUR, .pl is PLN, .ro is RON and .bg is EUR. A Ceneo feed with no such ending is read as PLN.
Categories
Every format brings its categories along as a path, written the way that format writes it: A > B in Google and Árukereső feeds, A | B in Heureka feeds and A/B in Ceneo feeds.
Where do I find my feed link?
Under the Feed link field, a collapsed Where do I find my feed link? gives one line for each common shop system:
| Shop system | Where the link is |
|---|---|
| Shoprenter | Marketing → Automatikus termékmegosztás → Árukereső: copy the feed link. |
| UNAS | Beállítások → Külső kapcsolatok → Árösszehasonlító export, Feed: switch on the Árukereső or Google export, add 46.225.128.253 as the Ügynökségi IP, save, then copy the link. UNAS can take a few hours to apply it. |
| Shoptet | Propojení → XML feedy: copy the Heureka or Google feed link with its security hash. |
| Wix | Google Merchant → Get Data Feed → Copy. |
| WooCommerce or Shopify | Choose the Shopify or WooCommerce shop type instead; it reads every version, price and stock by itself. |
| Other systems | Your Google Shopping, Heureka or Ceneo feed module shows the link. |
When a feed cannot be read
A feed that fails shows Needs attention, and one of two lines can appear under its row. Both end with a Contact us button, which copies the feed link and opens our support chat, so you can paste it there.
| Line under the row | What it means |
|---|---|
| Yaplet can't read this feed's format. It reads Google Shopping, Heureka, Árukereső and Ceneo feeds. | The link is not a product feed (a web page, for instance), or it is in a format Yaplet doesn't read. Use a Google Shopping, Heureka, Árukereső or Ceneo feed from your shop system, or write to us. |
| Your shop refused to let Yaplet read this feed. … | Your shop's server turned our reader away. Some shop systems, UNAS for example, let only listed addresses read their feeds. Allow 46.225.128.253 in your shop's feed settings, then choose Fetch now. |
As with any failed read, three in a row stop the source and email the organization's owner (see What happens when a read fails below). The line goes away as soon as a read succeeds.
Products from your website
When Yaplet learns your website (on the Knowledge screen), a page that publishes product data with a price — the details a shop page gives search engines — can become a product, with its name, price, stock and picture. These products go into a source of their own, Your website, which Yaplet makes by itself: there is nothing to add, no address and no schedule. A page that lists several priced products, such as a category page, stays an ordinary page.
- Refresh says At least once a week: a product is updated whenever its page is read again. The line under the name says what this source can't do (up to 2,000 pages per site; for hourly updates or a bigger catalog, use a Product API or feed source, or contact us).
- It has no Fetch now, Edit or Delete.
Switching it on or off
Every website has one switch, Pages with product data: on, I learn them as products, with their prices; off, I learn them as pages, like the rest of your site. Turn it off for a service business whose pages show a price but aren't products to sell. You can flip the same switch in three places:
- The row's ⋯ menu: Learn them as pages instead, or Learn them as products instead while it's off. Both ask you to confirm first.
- Add source → Your website → Continue: the Products from your website window lists each of the brand's websites with its switch, Pages with product data on (site). A flip saves at once; Done closes the window. If the brand has no website yet, the window says so, and Open Knowledge takes you to where you add one.
- Knowledge: the website's Manage pages window.
The change isn't instant: each page changes over the next time it is read. While the site is switched to pages, its row says Learned as pages now: these products leave one by one as I read the pages again. Switched back on, the pages become products again as they're read.
Fields that become keys
This is the setting that connects your catalog to your claims and instructions.
A claim or an instruction applies to a product when the two share a key. A product gets its keys from two places: the rule_keys list your shop sends with it, and the values of any product fields you name here.
So if your shop sends an Ingredients field and you add Ingredients to this box, every ingredient becomes a key on that product — and any claim or instruction carrying that ingredient's name applies to it automatically, from the Claims and Instructions tabs alike.
The rules sentences a Product API source sends with a product are something else: they are not keys, and they go to your AI as that product's own instructions whenever it is part of an answer.
Changing this setting re-derives the keys of every product of that source immediately. There is no refresh to wait for and nothing is re-read.
If the source keeps failing
This choice only takes effect once reading has stopped after three failures in a row.
Products you switched off by hand are never switched back on by this.
What happens when a read fails
Within a single read we try three times — 30 seconds each, waiting 5 then 15 seconds between attempts — but only when the problem looks temporary (a timeout, a network error, or a server error on your side). A rejection like "not found" or "forbidden" fails at once.
Then:
| What happens | |
|---|---|
| 1st and 2nd failure in a row | Status Needs attention. We keep retrying every hour. Nobody is told. |
| 3rd failure in a row | Status Stopped. Scheduled reading stops. Your organization's owner gets a notification and an email. |
Two things do not count as strikes: a Fetch now you ran yourself (it only sets Needs attention, and nobody is emailed), and a failed push from your shop (it shows in the run report only).
The email you get
One email per organization per hour, however many sources are involved — it cannot nag you. It tells you what happened, why, how to fix it, and what happens if you do nothing, with a button straight to this page.
Fetch now
Fetch now in the row's ⋯ menu reads the source immediately, in the background. It cannot run on a push-only source (there is no address to read).
- There is a five-minute cooldown per source. Inside it, you are told how long is left (for example Fetch now is available again in 3 minutes).
- It is also how you restart a stopped source: a successful manual read clears the strikes, sets the source back to Active, and brings back any products that were hidden.
The last run report
Last run report in the row's ⋯ menu opens the report for the most recent run, titled Last run — (the source's name). Until a source has run, the entry is grayed out and reads No run report yet. Only the latest run is kept for each source — read it before you trigger the next one.
It shows whether the run succeeded, is still running or failed; what started it (Scheduled read, Fetch now, Pushed by your shop, or Read from your website for a Your website source); whether it was a Full snapshot, Changes only or a Full replacement; and a grid of counters.
The ones worth knowing:
| Counter | What it means |
|---|---|
| Items received / Items used | How many products arrived, and how many survived validation. |
| Products added / updated / unchanged / removed | What changed at the base-product level. |
| Versions stored / Versions removed | The same, for versions. On a healthy run this is at least as large as the product count. |
| Search card pieces indexed | How much searchable text the AI re-read. A product becomes one to a few pieces depending on how much it carries. |
| Overview pages rewritten | The catalog pages that were rebuilt — one for the catalog as a whole, plus one per category. |
| Waiting for credit / Waiting for a plan | Products left out of this run because the workspace is at its 500-credit line (Waiting for credit) or has no room for more (Waiting for a plan). They are not stored and are tried again on the next run. These two counters show only when products were left out. |
| Skipped as invalid | Items that were left out. The reasons are listed underneath. |
| Versions that stopped a product | A version that failed validation takes its whole product out of the run, so this being non-zero explains a missing product. |
| Product prices ignored (versions sent) | You sent a price on the product and versions underneath it. The versions win and the product-level price is ignored — see the Product API reference. |
| Search terms cut for length | A product sent more search terms than one product may carry; the rest were dropped. |
Below that, up to three lists:
- Skipped items — which items were left out and why (the first 50).
- Products cut for length — products that sent more keys or more search terms than one product may carry.
- Fields the shop sent — every field name seen in this run. This is the same list the "fields that become keys" chips come from.
Row actions
Every row ends in a ⋯ menu (More actions) with Fetch now, Edit, Last run report and Delete — plus two more on Product API sources: Copy push address, and API guide for this source, a shortcut to the API tab with that source already selected, so the code samples carry its real address. A Your website row has only Last run report and its switch (Learn them as pages instead or Learn them as products instead).
Learning order and the 500-credit line
Every source teaches your AI its best products first: your shop's own priority, then popularity, then review count, then rating. A WooCommerce shop is read best sellers first, and its ratings and review counts come along. A Shopify shop list is read best-selling first when credit is short. A product feed carries none of these columns, so its products are learned in the order of the file. A Your website source goes by review count, then rating, then page order.
When your workspace pays from credit (your free 14 days, or bought credit, without a plan), learning stops while fewer than 500 credits are left, so the credit that remains goes to answers. The Add source form says so: Products are learned best sellers first, until 500 credits are left; the rest wait for credit. At that line:
- Products your AI already knows still update their price, stock and versions, at no cost. Fetch now and Product API pushes keep working too.
- New or changed products that don't fit wait. They are not stored (a new product does not show up yet) and are tried again on the next run.
- A source is never stopped, emailed about or switched off for lack of credit.
- The row's Products cell says what is waiting: Learned 40 of 100 products. The rest wait for credit. After you add credit, a source with a schedule goes back in the queue, and its waiting products are learned again within about an hour.
Some older free workspaces have a limit on searchable pieces. It works the same way: what does not fit waits, and the row says Learned 40 of 100 products. Choose a plan to learn the rest.
Limits worth knowing
| Limit | Value | What you see if you hit it |
|---|---|---|
| Products per source | 20,000 | The read fails and asks you to split the catalog across several sources |
| Versions per product | 500 | The product is skipped as invalid. A shop source keeps the first 500 instead, and a product feed keeps the first 500 rows of a group and skips the rest as invalid |
| Rows in a product feed | 5 for each product a source may hold (100,000) | The read fails: the feed has more rows than one source can read |
| Response size | 50 MB | "The response is larger than 50 MB" |
| Read timeout | 30 seconds per attempt | "The request timed out after 30 seconds" |
| Extra headers | 20 per source | The Add header button stops |
| Fields that become keys | 20 per source | The box stops accepting more |
| Keys per product | 500 | Counted as "Keys cut for length" in the report |
| Search terms per product | 100 words, versions included | Counted as "Search terms cut for length" in the report |
| Category depth | 6 levels, 100 characters each | The item is skipped as invalid |
| Description per product | 20,000 characters | The item is skipped as invalid |
| CSV columns | 100 | The read fails: "The CSV has … columns; a product feed has at most 100." |
Your workspace also has generous overall limits on products, versions and sources, set far above normal use. If you ever reach one, the read or the save fails and says so. Write to [email protected] to have it raised.
Smaller limits while nobody is paying
An organization with no active subscription and no credit balance gets smaller feed limits:
| Limit | While nobody is billed | On a paid plan or with credits |
|---|---|---|
| Response or push size | 5 MB | 50 MB read / 25 MB push |
| Products in one read or push | 1,000 | 20,000 |
| Pushes per minute | 6 | 60 |
Adding credits or starting a subscription lifts these immediately — there is nothing to switch on and nothing to wait for.