Facebook Shop and PrestaShop: Selling on Social Media

A Facebook Shop is the storefront that sits on your Facebook Page and Instagram profile — a browsable grid of your products, pulled from a catalog, that lets someone tap a product, see its details and either buy on the spot or get sent to your store to check out. That last fork is the whole game for a PrestaShop merchant, and it usually breaks the wrong way: outside the United States, "buy on the spot" mostly doesn't exist, so a Facebook Shop is really a discovery window that funnels people back to your PrestaShop checkout. Set it up without understanding that, and you build a shopfront that looks like it sells but actually just hands traffic to a checkout you may not have prepared for it.

Last updated: June 2026.

This guide is specifically about the Facebook Shop surface: how to get your PrestaShop catalog into it, the on-platform-versus-redirect checkout decision that defines what the Shop can do for you, and the PrestaShop-side work that decides whether the traffic it sends converts. It is not about Pixel tracking, ads or Instagram feeds — those are their own jobs, and they have their own guides linked at the points where they matter. If you're still deciding whether social commerce is even where your audience is, start one level up with which platforms actually drive sales.

What a Facebook Shop actually is (and what it isn't)

The terminology is a mess because Meta keeps renaming things, so here is the plain version. Your products live in a catalog inside Commerce Manager (business.facebook.com/commerce). A Shop is a presentation layer built on top of that catalog — collections, a cover, featured products — that appears on your Facebook Page and, if you connect it, your Instagram profile. The Shop doesn't hold your products; it shows the catalog. Get that mental model right and most of the confusion disappears: when a product is wrong in your Shop, the fix is almost always in the catalog or its feed, not in the Shop layout.

What a Facebook Shop is not: it is not a replacement for your PrestaShop store, it is not where your orders, customers or payment methods live (outside on-platform-checkout regions), and it is not a tracking or advertising tool. People conflate "set up a Facebook Shop" with "install the Pixel and run ads" — those are separate projects. The Pixel question is covered in why you need the Facebook Pixel even without ads, and the ad side in the practical Facebook and Instagram ads guide. This post stays on the Shop itself.

The decision that defines your Shop: on-platform vs. redirect checkout

Before you touch a feed, settle this, because everything downstream depends on it. A Facebook Shop can finish the sale one of two ways, and which one you get is mostly decided by your region, not your preference.

So what does this mean for a European PrestaShop merchant? Outside the regions where on-platform checkout is offered you will typically be on redirect checkout — confirm your current eligibility in Commerce Manager — which means your Facebook Shop's real conversion rate is set by your PrestaShop checkout, not by anything in Commerce Manager. The Shop's job ends at the tap on "View on website"; your store's job starts there, on a phone, for a visitor who came in cold from a social scroll. That is the part most merchants neglect, and it's where the orders leak. More on it below.

Getting your PrestaShop catalog into the Shop

The Shop is only ever as good as the catalog feeding it. You have three realistic ways to get PrestaShop products into Commerce Manager, and they suit very different stores.

For all but the smallest shops the scheduled feed URL is the right call: PrestaShop (or a feed module) generates a product feed at a stable URL, and you paste that URL into Commerce Manager under Catalog → Data sources → Use a data feed, then pick a fetch schedule. Set the fetch to every 6 hours at most, and hourly if your stock moves fast — a too-slow schedule is the single biggest cause of "in stock on my store, sold out on Facebook" embarrassment.

The feed fields PrestaShop has to populate correctly

Meta's product feed spec requires a fixed set of fields, and the failure mode is always the same: a field your feed leaves blank or fills wrong, multiplied across thousands of products, gets that whole slice of your catalog rejected. The required core:

• id — a stable unique identifier. Use the PrestaShop product ID or, better, the product reference so it survives across stores and languages.
• title — product name, front-loaded with the words a buyer would actually use (Meta truncates).
• description — clean text; strip HTML if your feed doesn't.
• availability — in stock / out of stock / preorder, driven from real PrestaShop stock, not a static value.
• price — with currency, and here is the trap: it must match what the customer sees on the product page, including or excluding VAT exactly as your store displays it. A feed sending ex-VAT prices to a tax-inclusive store shows a lower price on Facebook than at checkout, and that price jump at the redirect kills the sale.
• link — the canonical PrestaShop product URL (add UTM parameters here so you can separate Shop traffic from ad traffic in analytics).
• image_link — main image, 500×500 minimum, ideally 1000×1000.
• brand, condition — manufacturer name and new/used/refurbished.

Worth adding because they materially help: sale_price (so promo prices show with the strikethrough), additional_image_link, product_type (your PrestaShop category tree), and google_product_category. A PrestaShop store that runs multiple shops or languages needs to decide which one feeds the catalog — feeds silently mixing currencies or languages are a common, hard-to-spot mess.

Official Meta module or a feed module?

An official or partner "Facebook"/Meta connector may be available for some PrestaShop versions, wiring up the catalog, Shop and Pixel together — but verify the current module listing, the versions it supports, and the permissions it needs before relying on it, since Shop setup and approval still happen in Commerce Manager regardless. Check version support against your PrestaShop release (1.7.x, 8.x or 9.x) before relying on it — version support has historically lagged, and a half-working connector that occasionally drops your whole catalog is worse than a plain feed URL. If you only need the Shop (not on-platform checkout), a dedicated product-feed module that outputs a Meta-spec feed at a stable URL is often the more reliable, lower-bloat choice: you control the fetch schedule, the field mapping and the multi-store logic, and there's nothing injecting scripts into your theme that you didn't ask for.

Building the Shop itself in Commerce Manager

With the catalog flowing, the Shop is the easy part — and deliberately so. In Commerce Manager you create a Shop, choose the checkout method your region allows, connect your Facebook Page (and Instagram Business account if you want the Shop on Instagram too), and organize products into collections. Collections are the one piece of curation that earns its keep: rather than dumping 4,000 SKUs into one grid, build a handful of themed collections — bestsellers, a seasonal edit, a price-point range — because a Shop someone can actually browse converts better than a wall of products. Then submit the Shop for review; approval typically takes a few days, and most rejections trace back to catalog or policy issues, not the Shop layout.

If your goal is broader — pulling your Instagram and Facebook content into your storefront, or tagging products across feeds and stories rather than running a formal Shop — that's a different integration with its own setup. We cover it in integrating Instagram and Facebook feeds with PrestaShop, and the narrower question of whether an embedded Instagram feed actually converts in Instagram feed on your store.

The part that actually decides your revenue: the PrestaShop checkout the Shop redirects to

For a redirect-checkout Shop — which, again, is essentially every EU/UK store — the Facebook Shop is a referral machine and nothing more. It cannot improve your conversion rate; it can only deliver visitors to a page you control. So the honest version of "how do I make my Facebook Shop sell" is: make the page it sends people to sell. Three things matter disproportionately here, because Facebook traffic is overwhelmingly mobile and arrives with low intent:

• The redirect lands on a fast, mobile-clean product page. Someone tapping through from a feed expects an instant, native-feeling page. A heavy theme, a slow first load, or a layout that fights a thumb loses them before they read the price.
• Guest checkout, minimal steps. A cold social visitor will not create an account to buy a 30-euro item. Forced registration and a multi-page checkout are where Facebook traffic evaporates fastest.
• Price honesty across the hop. The number they saw in the Shop must be the number on the product page must be the number at checkout. Any surprise at the redirect reads as a bait-and-switch.

This is the single highest-leverage area for social traffic, and it's a deep enough topic to have its own treatment — if you want the orders your Shop is sending you to actually close, the work is on the checkout. Our Checkout Revolution module turns PrestaShop's stepped native checkout into a true single-page, guest-first flow that holds up on mobile, so the cold visitor your Facebook Shop redirects in meets the fewest possible reasons to bail. The reasoning and the wider checkout science are in Checkout Revolution 3.0.

Where the Shop ends and other channels begin

A Facebook Shop on its own is organic discovery — useful, but a slow burn. The pieces that turn it into a system are deliberately not part of Shop setup, and trying to do them all at once is how merchants end up with a broken Pixel, a stale catalog and a Shop nobody curated. Tackle them as separate, sequenced jobs:

• Tracking. The Pixel (and server-side Conversions API) is what lets you measure and later retarget Shop and site visitors. The browser Pixel alone increasingly under-reports — ad blockers and Safari's tracking limits drop events — so pairing it with the server-side Conversions API, which sends the same purchase and view events from your server, is now how you keep match quality up. Both must be gated behind cookie consent in the EU/UK. Wiring the Pixel and CAPI together by hand is fiddly; Marketing Revolution handles both from one screen with consent honoured. It's a prerequisite for ads, not for the Shop — set it up on its own terms: Facebook Pixel for PrestaShop, and the broader social-tag landscape in social tracking explained simply.
• Paid amplification. Dynamic ads that re-show catalog products to people who viewed them are where most social revenue actually comes from — but that's an ad campaign sitting on top of your catalog, covered in Facebook and Instagram ads and the mechanics of follow-you ads in retargeting explained.
• Social proof on your own store. Showing your Facebook activity to site visitors, or letting them sign in with Facebook, are storefront features, not Shop features — see Facebook posts on your store and social login for PrestaShop.

Common Facebook Shop failures (and the PrestaShop-side cause)

Almost every Shop problem traces back to the catalog or the feed, which means the fix lives in PrestaShop, not Commerce Manager:

• "Out of stock" on Facebook, in stock on your site. Feed fetch interval too slow, or the feed sending a static availability value. Tighten the schedule to 6 hours or less and make sure availability is driven from real stock.
• Price mismatch at checkout. VAT handling differs between your feed and your product page. Align them so the feed price equals the displayed price exactly.
• Products rejected on upload. Promotional overlays, watermarks, misleading or policy-violating text on images, or policy categories (supplements with health claims, alcohol, weapons, adult). Use clean product images, avoid promotional text and watermarks, check Commerce Manager diagnostics, and screen your catalog against Meta's commerce policies before submitting.
• Whole feed failing. A required field empty across the catalog — usually brand, condition or a broken image_link. Check the feed's diagnostics in Commerce Manager; it tells you which field and how many products.
• Catalog approval rate low. Aim to keep the large majority of products active and approved (e.g. 95%+). A persistently low rate means a systematic feed-mapping bug, not bad luck with individual products. Don't confuse this with the separate event/content-ID match rate in Pixel/Conversions API diagnostics, which measures how well your tracked events match catalog items for ads and retargeting — a different metric with its own fixes.

FAQ

Can EU customers buy directly inside my Facebook Shop?

Usually no. On-Facebook checkout is limited to certain regions (such as the US) at time of writing, so outside them your Shop runs on redirect checkout — the customer taps "View on website" and finishes the purchase on your PrestaShop store. Confirm your current eligibility in Commerce Manager, but plan as if your Shop is a discovery window that funnels people back to your own checkout.

What's the best way to get my PrestaShop catalog into Commerce Manager?

For all but the tiniest stores, a scheduled feed URL: PrestaShop (or a feed module) generates a Meta-spec product feed at a stable URL, you paste it under Catalog > Data sources > Use a data feed, and set a fetch interval. Manual CSV uploads go stale the moment you change a price; real-time API push is worth it only for large or fast-moving catalogs.

Why do products show "out of stock" on Facebook when they're in stock on my site?

Either the feed fetch interval is too slow or the feed is sending a static availability value. Tighten the schedule to 6 hours or less and make sure the availability field is driven from real PrestaShop stock, not hard-coded. Stale availability is the most common and most embarrassing Shop bug.

Why do my Facebook prices not match my checkout?

Almost always VAT handling. If the feed sends ex-VAT prices to a tax-inclusive store, the Shop shows a lower number than the product page and checkout, and that jump at the redirect reads as bait-and-switch and kills the sale. Align the feed's price field to exactly what the product page displays, VAT included or excluded the same way.

Do I need the official Meta module, or is a feed module enough?

If you only need the Shop (not on-platform checkout), a dedicated product-feed module that outputs a Meta-spec feed at a stable URL is often the more reliable, lower-bloat choice — you control the schedule, field mapping and multi-store logic, with nothing injected into your theme. If you use the official connector, verify it supports your exact PrestaShop version (1.7.x, 8.x or 9.x) first; version support has historically lagged.

The order to do this in

Sequence beats ambition here. First, get a clean scheduled feed into Commerce Manager and confirm prices, stock and images are right — nothing else matters if the catalog is wrong. Second, build and submit the Shop with a few curated collections. Third — and this is the step merchants skip — make sure your PrestaShop product pages and checkout can actually convert the mobile, low-intent traffic the Shop will start sending. Only after those three are solid does it make sense to layer on the Pixel, retargeting and ads, each as its own deliberate job. A Facebook Shop doesn't sell for you; it points people at the page that does. Your work is making sure that page is ready when they arrive.