The Catalogue and the Feed: From Your Store to Every Platform
Your advert does not know your product. It knows a row in a table — and everything it decides comes from that row alone.
$109One-time purchase — lifetime access
One device and browser · free reset the same business day on WhatsApp · refund within 7 days if the content was never opened.
01 — Overview
Overview
The platform does not visit your store to understand what you sell. It reads a file you sent it — and if that file is incomplete, out of date, or written in your language rather than the buyer’s, that is what it will advertise about you. Which makes improving the feed the cheapest improvement in all of advertising: it changes your results without changing a budget, a keyword or an audience.
Four destinations come from the same file: shopping adverts, where the feed is the targeting itself rather than keywords you buy; dynamic adverts that show a visitor what they viewed; the conversation catalogue the customer sees before asking a price; and the structured data on your own pages. The course builds one source with a transformation per destination — never several lists that quietly drift apart.
And it covers what most feeds get wrong: an identifier that must never change or the product loses its history, titles written as the buyer types rather than as your internal name, the exact match between feed and page that prevents the commonest rejection, and the silent partial rejection where a third of your catalogue is refused while the dashboard says “updated”.
02 — What you will learn
What you will learn
What a feed actually is, and the four destinations that come from the same file
The three rules of the identifier — and why changing it deletes a product and creates another
The three layers of fields, and the neglected one that gets your variants rejected
Titles written as the buyer types, including Arabic in dialect, standard and Latin letters
The exact match between feed and page — and the price that is invisible without a click
Changing availability rather than deleting a product that ran out
One source with a transformation per destination, and the test that exposes hidden lists
Reading errors by cost rather than count, and the silent partial rejection nobody notices
03 — The lessons
The lessons
- What a Feed Is, and Why It Is Your Most Important File
- The Fields: What Is Required, What Helps, What Is Neglected
- The Title: The Field That Decides Who Sees You
- Image, Price and Availability: The Three That Get You Rejected
- From One Source to Many Destinations
- Updating: How Often, and What Happens When You Lag
- Errors: How to Read Them and What They Cost
- The Capstone: Your Map and the Audit
04 — What you get
What you get
8 interactive lessons in short sections
~4 hours including hands-on tasks
A 32-question audit + a ninety-day plan
One source feeding four destinations
05 — How buying works
No online payment — three simple steps
Send your request
Fill the short form: name, phone, email. This site never asks for any payment details.
I contact you personally
I confirm the details with you and arrange a single payment in cash or by local transfer — whatever suits you.
Your activation code arrives
A one-time code unlocks the product on one device and browser, with lifetime access. A new device or cleared browser data only needs a free reset, done the same business day on WhatsApp.
06 — Questions, answered
Questions, answered
I sell services, not products. Is this for me?
No, and lesson one says so in its first refusal: if you do not sell products with pages and prices — a service priced after a conversation, or work by the project — you have no catalogue, and you should go straight to the other advertising courses. A feed exists to describe items that have an identifier, a price, availability and a link. Without those there is nothing to feed.
Why does it name no platform or tool?
Because names change and the fields do not. Every platform needs an identifier, a price, availability, a link and an image, and none of them accepts a contradiction between what you send and what your page shows. Field names differ between platforms and change over the years; the needs behind them have not. The course also explains no interface buttons, for the same reason it refuses to name tools: a description of where a button sits becomes a source of error within a year, while a rule about what a feed must contain stays true.
Most of my products are rejected and I do not know why.
The reason is always written; the problem is that it goes unread. Lessons four and seven are built for exactly this. Most rejections come back to three fields — price, availability and image — and the most insidious is a price that is not visible on the page without a click or a login, because the platform does not click and does not log in, so it appears as a rejection with no cause you can see. Lesson seven then separates errors from warnings, ranks fixes by what they cost rather than how many there are, and gives the one comparison that exposes the silent partial rejection: your source count against the count active in the destination.
I keep a separate list for each platform. Is that wrong?
Yes, and lesson five is written about it. Multiple lists do not fall behind immediately, they drift gradually — and after months there are products in one destination and not another, different prices, and old images, and nobody notices until a customer complains. The rule is one source with a transformation per destination, and the test is one question: if I change a product’s price now, how many places must I open? The right answer is one, and any other answer means you have multiple lists even if you never called them that.
How does it relate to the accounts course?
The accounts course comes before this one, and lesson one says so. There is no point building a catalogue inside an account you do not own — its history, its data and its audiences would belong to someone else. Once ownership and structure are settled, this course fills that structure with a feed. Three other products are named and left alone: running campaigns is in the other advertising courses, the structured data on your product page is in the Technical SEO book, and how Arabic is actually typed in search is Local SEO chapter nine. And inventory accuracy itself — your stock in the system versus your stock on the shelf — is the Inventory book, because a lagging source is not a feed problem.
How do I pay and get access?
There is no online payment on this site. Send the request form, I contact you personally and arrange the payment with you (cash or local transfer), then you get a one-time activation code for one device with lifetime access.
What exactly am I buying, and what if something goes wrong?
A one-time purchase with lifetime access — no subscription and no renewal. Access is bound to one device and one browser: if you change device or clear your browser data, it needs a reset, which is free and done the same business day on WhatsApp. If you have not opened the content, you can ask for a refund within 7 days of your purchase. All of this is agreed before you pay, and no payment ever happens on this site.
07 — Send your request
Request your copy of The Catalogue and the Feed: From Your Store to Every Platform
Send your details and I will contact you personally the same business day to arrange the purchase — payment happens only after I have spoken with you, and no online payment is ever requested.