How to Upload Ecommerce Product Feeds for ChatGPT Shopping in Kenya
An online shop needs accurate product data before trying to appear in AI shopping experiences. Check current merchant eligibility, prepare a feed with real prices and working product links, then use the supported submission method. A feed does not guarantee product recommendations.
01 Start with the store, not the file
Before exporting anything, check that customers can buy the products on your website. Every product should have a clear name, accurate price, usable photo, stock information and a working checkout. A broken store does not become reliable because it has a neat CSV file.
For Kenyan retailers, confirm delivery areas, payment options and return terms on the site. If you accept M-Pesa, explain the checkout steps accurately. Do not claim that a product feed processes payments; it only supplies information about items.
02 Check whether your business can submit a feed
Business Hub features and merchant eligibility can change. Open the official merchant documentation and look at the options available to your verified business. Do not assume every Kenyan store can use every shopping feature or that a feed alone unlocks a Business Agent.
Keep business ownership clear. If an agency manages the shop, the owner should authorize the work and retain access to the business account. Avoid unofficial services that promise guaranteed placement.
03 Prepare products in a clean format
Use a stable product identifier, a specific title and the real product page URL. Prices and availability must agree with the website. Variations such as size and colour need to follow the current feed specification rather than being squeezed into a confusing product title.
A WooCommerce export is a starting point, not necessarily a ready-to-upload feed. Check the required column names, allowed values and image rules in the current specification. Test a small sample before submitting the entire catalogue.
04 Upload, read the results and fix errors
Follow the feed method shown in the merchant interface. Some systems accept uploaded files or hosted feed URLs. A hosted file should contain the actual product data, not a page explaining where the feed lives.
After submission, review validation errors carefully. A product may fail because of a broken link, missing field, incorrect domain or unsupported value. Correct the source data and submit again rather than changing random settings.
05 Keep the catalogue current
Stock and prices change. Assign someone to keep the feed and store in sync. A shopper who clicks an item advertised as available but finds it sold out is likely to lose confidence.
Track actual product visits and sales where your analytics allow. Do not promise that ChatGPT will recommend every uploaded item, and do not use one test question as proof that a store has achieved a permanent ranking.
06 A small test is better than a broken full upload
A shop with 800 products can begin with a small set covering a basic item, a variation and a discounted item. If those three types pass validation and match the website, the owner has learned more than from uploading all 800 at once and receiving hundreds of errors.
07 Common feed mistakes that waste time
One frequent problem is uploading the wrong kind of CSV. A file can open perfectly in Excel and still fail because the destination expects different column names or value formats. Check the exact current specification before changing your ecommerce database.
Another common problem is stale product links. If a shop has changed its permalink structure, exported URLs may redirect or lead to missing pages. Open a sample of links on a phone before uploading the feed.
08 Who should maintain the feed
The store owner should know who is responsible for stock, prices and product details. The website developer can handle the technical export, but the person managing inventory must provide accurate changes.
Agree on a routine for checking rejected items and unavailable products. A catalogue that is updated only when something breaks can quickly become misleading.
09 What to measure after launch
Use tagged product links where supported and review store analytics for visits and orders. A merchant dashboard may show processing information, but that is not the same as sales performance.
Ask customers whether they found the product details clear. Confusing variants, unclear delivery terms and hidden charges can prevent purchases even when product discovery works.
10 Decide which catalogue items belong in the first feed
Start with products that are genuinely available and have complete pages. Separate discontinued items, made-to-order products and items with uncertain stock. A merchant can technically submit thousands of rows, but customers will judge the store by whether the item they click is really available. Make a shortlist that includes ordinary products, variations and discounted products, then check each kind before expanding.
For a shop with 1,350 products, the first exercise is not to export 1,350 rows. It is to review a representative sample and confirm that the catalogue is clean enough to scale. Record problems such as duplicate SKUs, missing images and inconsistent prices in a simple sheet. Assign someone to fix the source records so the next export does not recreate the same errors.
11 Understand product identifiers and variations
A product identifier should continue to refer to the same item after routine updates. If a store changes identifiers every time it exports a feed, an external system may struggle to tell whether an item is new or simply updated. Decide how the store handles parent products and variations before generating the feed. A shirt in three sizes may need different records or attributes depending on the current feed specification.
Check the actual product pages for variation behaviour. If a customer clicks a red medium shirt, they should not land on an unrelated default colour with a different price. Also confirm how sale prices are represented. A feed showing KES 2,000 when the website shows KES 2,500 is not a small technical detail; it is a trust problem that may cause rejection or customer complaints.
12 Write titles that describe what is sold
Product titles should help someone recognize the item. A clear title may include the brand, model, product type and an important variation when relevant. It should not be a sentence stuffed with every Kenyan town or a list of unrelated search terms. Keep the language natural and make sure the title matches what the customer sees on the landing page.
Descriptions should explain the real product: material, size, compatibility, contents of the package and practical limitations. Avoid copying a manufacturer paragraph into hundreds of products without checking accuracy. For technical goods, include the model numbers and compatibility notes that prevent costly wrong orders. For furniture, measurements and delivery arrangements may matter more than promotional adjectives.
13 Check images before blaming the feed
Every image URL should open a real product image without requiring a customer to log in. Check for broken images, incorrect variants, very small thumbnails and watermarks that obscure the product. If the store recently moved domains, older image links may still point to the previous site. Test links in a private browser window rather than only while signed in to WordPress.
Use photos that accurately represent the item. A product should not be shown in a colour or configuration that the customer cannot order. Where a product has several views, keep the main image recognizable and use the website gallery to answer further questions. Good images support customer decisions, but they do not compensate for incorrect prices or unavailable stock.
14 Make delivery and return information clear
Kenyan customers may want to know whether an item can be delivered to Nairobi, Eldoret, Kisumu or a rural town, and whether the price includes delivery. Those questions belong on the store website even if they are not feed fields. A product feed should point to pages where buyers can understand the full transaction before paying.
Write return and exchange terms in plain language. If an item cannot be returned after installation or opening, explain the lawful conditions clearly. Avoid surprising customers with charges that appear only after checkout. Product discovery is only the first part of the journey; the website must make the rest of the purchase straightforward.
15 Choose an update routine the team can maintain
A feed uploaded once and forgotten can become inaccurate within days if stock moves quickly. Decide who changes product prices, who updates inventory and who checks the exported file. The best update frequency depends on how often the catalogue changes and what methods the platform supports.
If the store runs sales, schedule a check before and after the promotion. A discounted price should not remain in a feed after the offer has ended. Keep a record of the last successful update and a list of rejected items. A simple routine maintained consistently is more useful than a complicated automation nobody understands.
16 Read errors by category, not one by one
When a feed returns many errors, group them. A hundred missing-price errors may have one cause in the export mapping. Several broken links may come from the same incorrect domain. Fix the underlying pattern first, regenerate the file and check whether the total number of errors falls.
Separate warnings from blocking errors when the interface makes that distinction. Do not delete valid products simply to make an error count look smaller. Keep the source export and the processed results so the developer and store manager can see exactly what changed.
17 Connect the feed to a trustworthy checkout
A customer who discovers a product still needs a safe way to buy it. Test mobile checkout, address entry, shipping options and payment confirmation. If the store uses M-Pesa, check that the confirmation flow works and does not leave paid orders in an uncertain state.
Try placing a test order with an inexpensive product or an approved test environment. Check the order email and the stock adjustment. If the checkout is broken, fixing that issue should take priority over adding more products to the feed. The real goal is a successful customer experience, not simply a large catalogue.
18 Protect the account and product data
Only authorized people should manage the merchant account and feed delivery settings. Do not send account passwords through casual messaging or share identity documents with unverified third parties. Keep backups of the original product data and export mapping.
If an agency sets up the feed, the store owner should retain ownership of the domain and merchant account. Agree on how updates will continue after the project ends. A well-documented setup avoids a situation where nobody knows how to change a price or fix a rejected item.
19 Measure outcomes without claiming guaranteed recommendations
An accepted feed means product information has passed a processing step; it does not mean every product will appear in ChatGPT or generate sales. Measure real product visits, enquiries and completed purchases where reliable tracking is available.
Compare the experience before and after the feed using the same time periods where possible. Consider seasonality, promotions and changes in stock. If visits increase but sales do not, inspect pricing, delivery costs, product pages and checkout before assuming the feed is the problem.
20 Product feed troubleshooting guide
Use this as a working reference. Start with the situation closest to your own, then check the real account, website or customer process before making changes.
| Situation | Useful next step |
|---|---|
| A product has no SKU | Create a stable internal identifier before exporting; check that updates keep the same ID. |
| A variation has the wrong price | Compare each variant with its live product page; fix the source catalogue. |
| An image fails to load | Open its URL without logging in; check domain changes and permissions. |
| A product page redirects | Confirm the final destination is the right item, not a generic category. |
| Stock changes every day | Use a supported update method that matches the shop’s real inventory process. |
| A feed is rejected | Group errors by type and fix the export mapping before resubmitting. |
| Prices use inconsistent currency | Check feed currency rules and match the live checkout. |
| A product is discontinued | Remove or correctly mark it rather than leaving it available. |
| The owner cannot access the feed | Transfer documentation and legitimate account access to the authorized business owner. |
| Feed accepted but no sales | Check product pages, delivery terms and checkout before assuming the feed is ineffective. |
21 A shop with changing stock
Consider a store selling electronics and accessories. Its stock changes every afternoon, but the owner exports a feed only once a month. Customers may discover items that were sold weeks ago. The better approach is to connect the export routine to the actual inventory process, check which update methods are supported and assign responsibility for failed updates. Before publishing, compare a sample of feed rows with the live product pages and the stock system. This avoids turning a product discovery channel into a source of complaints.
22 A product with several prices
A furniture store may sell a table in different sizes. The product page shows a starting price, but the larger size costs more. A feed that sends only the starting price while linking to the larger variant may mislead shoppers. Review how the platform represents variants and make sure the submitted price corresponds to what the buyer can actually select. If the specification cannot express a particular configuration clearly, do not guess. Read the current rules and test the customer path from the product link to checkout.
23 When a catalogue is copied from suppliers
A merchant might import hundreds of supplier descriptions that contain outdated measurements, foreign delivery promises or product images it has no right to use. Those problems should be corrected on the store itself before the feed is prepared. Build a simple content review that checks important specifications, local delivery arrangements and image permissions. A clean feed begins with trustworthy source data; formatting a CSV cannot turn incorrect product information into a reliable offer.
24 A failed upload with many errors
Suppose 600 items are rejected because the export uses a field name the destination does not recognize. Editing each row separately would waste hours. Inspect the error summary, compare the file headers with the current specification and fix the mapping once. Then regenerate a small test file. Only after it passes should the owner retry the full catalogue. This method also creates a repeatable process for future exports rather than a one-off rescue.
25 What a buyer sees after clicking
The feed may contain perfect data, but a buyer can still reach a slow page with a confusing price and no clear delivery information. Open the item link on a phone and follow the purchase journey. Check that the selected variant matches the advertised item, the total is understandable and the payment process completes. If a store cannot process an ordinary order reliably, improving product feeds should not be the first priority.
26 Handling a promotional sale
A Kenyan shop may announce a weekend discount across its website and social pages. If the feed still shows the previous price, customers may receive conflicting information. Prepare the promotion in advance, confirm how sale prices are represented and check the feed after the sale begins. When the offer ends, update the source catalogue and confirm the feed follows. Document who is responsible so price corrections do not depend on remembering them at the last minute.
27 When an agency manages the setup
A developer can configure export tools, but the retailer remains responsible for accurate products and customer service. Agree on who controls the merchant account, who approves catalogue changes and who investigates rejected items. Hand over the field mapping and update instructions in plain language. If the developer leaves, the owner should still be able to correct a product price and understand where the feed is generated.
28 Judging whether the work helped
A feed can be accepted without producing measurable sales. Look at available product visits and real orders, but also inspect the store’s broader performance. Was delivery too expensive? Were popular sizes unavailable? Did checkout fail on mobile? Those issues may matter more than feed formatting. Avoid claiming that a merchant has achieved an AI ranking simply because its products were uploaded successfully.
29 How to decide which products to fix first
Prioritize products that customers already buy or enquire about, because an error on a popular item has a greater practical cost. Next address entire groups affected by the same export problem. If all variation products lack a required attribute, fix the mapping rather than editing individual items. Then review lower-demand products in manageable groups. Keep a record of what was corrected, who approved the change and whether the next export passed validation. This approach makes a large catalogue project understandable to the store owner.
30 Why a product feed needs a responsible person
Automation is useful, but it cannot decide whether a supplier delivered the wrong size or whether a discount should continue after a promotion. Assign a person to confirm inventory and pricing changes, even if software generates the file. The developer should explain how errors are reported and how to stop publishing inaccurate data. If no one owns that process, a technically successful feed can quietly become a misleading catalogue. The store needs a maintenance routine that matches its staffing.
31 What to do when the platform changes its rules
Feed specifications and business eligibility may change. Save a copy of the version used when the integration was built, but always check the current official instructions before a major update. Test changes on a small sample and verify that accepted items still lead to correct product pages. Avoid relying on a social-media tutorial that assumes every merchant sees the same settings. If a field is unclear, confirm its intended meaning before inventing a value just to make the file pass.
32 A final pre-launch customer test
Choose a product from the submitted feed and act like a first-time buyer. Open the link without being signed in, select the exact variation, check the final price, review delivery information and attempt a safe test checkout. Repeat on a phone. Note anything that would make a real customer hesitate. This exercise catches practical problems that a CSV validator cannot see. The purpose of the feed is to connect shoppers to reliable product information, not merely to satisfy a technical upload screen.
Questions people often ask
Can Kenyan online stores submit feeds?
Only where the current merchant feature and eligibility requirements allow it; check the options available in your account.
The practical test is whether the current Business Hub account actually offers merchant submission. Check ownership, business identity and the product-feed instructions in the official interface before paying for a tool. A shop should not promise customers that its products are available in ChatGPT just because an export file exists.
Can I upload WooCommerce CSV directly?
Not necessarily. Match its fields to the current required feed format first.
Start by comparing the exported columns with the current specification. WooCommerce fields, variable products, image links and availability values may need mapping. Test a handful of real products first, including one variation and one discounted item, and check the validation response before sending the entire catalogue.
Does a feed guarantee sales?
No. It supplies product information but does not guarantee visibility, clicks or purchases.
An accepted file means information has been supplied, not that customers will see or buy every item. Sales still depend on the product, price, availability and website experience. Track visits and actual orders where reliable data is available, and avoid calling a single AI answer a permanent ranking.
Should prices be in Kenyan shillings?
Use the currency formats supported by the current specification and make sure they match your live store.
Do not assume a currency is accepted simply because the store displays it. Check the allowed currency values and market requirements in the current specification. If conversion is needed, do not silently change prices or display a figure that differs from the amount customers pay at checkout.
What if some products are out of stock?
Use accurate availability values and update them when stock changes.
Update the availability field to reflect the real store. If stock changes frequently, establish an update schedule that the team can maintain. Customers should not reach a page advertised as available only to discover that the product cannot be purchased.
Can I use a hosted feed URL?
Use it if the current merchant interface supports that delivery method.
A hosted feed is useful only when the current merchant setup accepts that method. The URL must return the feed file in the expected format, remain accessible to the service and reflect updated product details. A normal product-category webpage is not a feed URL.
Do I need a working website?
Yes, a reliable store and accessible product pages are essential for customers.
The website is where the customer checks specifications, delivery terms, stock and payment. Test the product link and checkout on a phone, not only on the store administrator’s computer. A feed cannot repair a broken checkout or unclear return policy.
For current platform rules, consult the official platform guidance before making changes. Features and eligibility may change.
