Crosslist from PrestaShop to Facebook Marketplace — Automatically

On this page

• Why put a PrestaShop catalogue on Marketplace at all
• The gap: nothing else does this
• The local-pickup reality in Europe
• What changed when Meta ended native checkout
• Fees, and why we are not printing a number
• How to crosslist from PrestaShop to Marketplace
• Field mapping — product to listing
• Combinations, and the multiplication problem
• Getting listings approved and keeping the account
• What syncs and what does not
• Sources and verification
• Related guides

Why put a PrestaShop catalogue on Marketplace at all

Because it is free to list, the audience is enormous, and it reaches people who will never find your store.

PrestaShop is a genuinely European platform. Store Leads counts about 149,980 live PrestaShop stores, with France at roughly 14.8%, Spain 10.3%, Poland 8.9% and Italy 7.4% — four countries accounting for around 41% of all of them. That is a merchant base of independent European retailers, most of them competing for search traffic against much larger sites. Marketplace’s audience is not search traffic; it is people browsing what is near them, which is a different demand entirely.

The honest framing, though, is the one most write-ups skip: this is not a mirror of your webshop. Given the location constraint and the delivery gate below, what you are actually building is a local sales channel that happens to share a catalogue with your online one. A PrestaShop merchant shipping nationwide gets, through Marketplace, a way to put stock in front of buyers in their own town. Those are different sales rather than the same sales through a second window.

Worth being clear-eyed about the platform’s direction too. PrestaShop’s own homepage claims more than 250,000 merchants; Store Leads counts 149,980 live stores and records a 15% year-on-year decline. Both numbers are real and they measure different things, but the trend is worth knowing if you are deciding how much to invest in channels around a PrestaShop store.

The gap: nothing else does this

PrestaShop has an official Facebook module, ps_facebook — “PrestaShop Social with Facebook & Instagram”. It is maintained but minimal: the latest release is v1.38.19 from 5 August 2026, with five commits across 2026. Its scope is the Facebook Pixel plus catalogue sync via the Facebook Business Extension, feeding Shops and Instagram. The word “marketplace” appears in its documentation only in the sense of PrestaShop’s own addons store.

The third-party modules do not close the gap either. The well-known Facebook modules from the main PrestaShop vendors are shop-page and catalogue-feed modules; where one of them says “marketplace” it generally means its own multi-vendor marketplace feature, not Meta’s. Feed tools connect PrestaShop to Meta’s Commerce Manager as a catalogue, which is a different destination from a Marketplace listing.

Nor is there an API to fall back on. Meta provides no public route for creating personal Marketplace listings — its catalogue and Commerce APIs serve Shops and advertising, and the business-side Marketplace catalogue route is a restricted, eligibility-gated programme rather than something a European merchant can switch on.

So the practical position for a PrestaShop merchant in 2026 is that Marketplace listings are created by hand, one at a time, through Meta’s own interface, which offers no bulk tooling. For a catalogue of any size that is not a workflow, and that is the specific problem worth solving.

The local-pickup reality in Europe

This is the constraint to understand before anything else, because it determines what kind of channel you are building.

Meta’s own help pages on selling with delivery return, to European visitors, a message rather than instructions: “Selling with delivery on Marketplace isn’t available in your location at the moment. Learn how to sell something locally on Marketplace.” A second article says the same in different words. This is a persistent gate rather than a temporary outage — archived copies of the same page show the identical block.

What that means in practice for a merchant in France, Spain, Poland or Italy is:

• Your listings are discovered by proximity to the buyer, not by search intent.
• The transaction ends with somebody collecting the item and paying you directly. Meta never sees the money.
• There is no Marketplace checkout, no Marketplace postage, no tracking and no payout.
• There is consequently no order to sync back to anything, and no sale anyone can report to you.

None of that makes the channel worthless — it makes it a specific thing. Bulky goods you would rather not ship, stock you want to clear locally, end-of-line items, anything where a customer collecting is a saving rather than an inconvenience: those are what Marketplace is genuinely good for from a PrestaShop catalogue. Trying to run it as a nationwide shipped channel is fighting the platform.

We are describing the gate as we observed it, from Europe, on 5 September 2026. Which countries do have Marketplace delivery is not something Meta publishes as a list, and we are not going to guess at one.

What changed when Meta ended native checkout

In September 2025 Meta made a change that is under-reported and, unusually, works in a PrestaShop merchant’s favour. Its own page states: “As of September 2025, Shops on Facebook and Instagram now use website checkout. If your shop used checkout on Facebook or Instagram, the checkout method has been updated or your shop is invisible.” Buyers are now “directed to your own website to complete the purchase”, and management of the post-purchase experience in Commerce Manager has been discontinued.

For a merchant with a real storefront this removes an old dilemma. There is no longer a question of whether to run a parallel Meta checkout with its own orders, payouts and post-purchase handling sitting outside your shop. The Shops surface has become a shop window that sends people to your PrestaShop checkout, where your tax rules, your shipping profiles, your customer accounts and your order history already work.

It also clarifies the two surfaces. Shops is a catalogue-driven storefront on your Page that now points at your website — and that is what ps_facebook feeds. Marketplace is the local classifieds surface, listing by listing, with no checkout in Europe at all. They are different products and the tooling for one does nothing for the other.

Fees, and why we are not printing a number

Two different Marketplace selling fees circulate widely, both attributed to Meta, and they disagree by a factor of two. Meta’s own fee documentation now sits inside the same geo-gated article set described above, so it cannot be read from Europe, and the archived copies are geo-blocked as well.

We are therefore not quoting a percentage. A wrong fee on a page like this is not a cosmetic error — it is a number a merchant prices against.

What can be said with confidence:

• Local pickup listings carry no selling fee. Meta is not in the transaction, so there is nothing to charge.
• Listing is free in every case.
• Shipped-order fees apply only where Marketplace delivery is available, which for most European sellers is nowhere — so for the readership of this page the practical answer is that Marketplace costs nothing.
• If you are in a market where delivery is available, read the fee from Meta’s own commerce pages in your own market before you price anything.

PrestaShop’s own costs are the other half. The software is open source and free to self-host; PrestaShop also sells a hosted edition on a monthly subscription, currently based on the PrestaShop 8 line rather than 9. Your real costs are hosting, modules and developer time — and PrestaShop’s most consistent criticism on review sites is exactly that: paid modules for functionality merchants expect to be included.

How to crosslist from PrestaShop to Marketplace

1. Turn the PrestaShop Webservice on. It is disabled by default. Enable it under Advanced Parameters → Webservice and generate a key.
2. Connect PrestaShop in FLUF Connect using your Webservice key.
3. Import your catalogue. FLUF reads products, combinations, images and stock, and builds one master record per sellable item.
4. Connect Facebook. Marketplace is an extension-first channel: it runs through the FLUF browser extension, or through the FLUF mobile app, which hosts the session on your own device.
5. Set condition and choose what to list. Do not push the whole catalogue — see the combinations section.
6. Publish. Listings are created through your own logged-in session, with your location attached.
7. Keep sold-out protection on, because a Marketplace sale will never tell you it happened.

The initial catalogue import includes product photos and may take time for a large store. Wait for it to finish before reviewing your listings.

Field mapping — product to listing

The last row is the load-bearing one. Nothing in a PrestaShop product carries geography, because a webshop’s inventory is national or continental. A Marketplace listing exists somewhere and is surfaced to buyers by distance. That is not a field you can map; it is a property of the account and the listing, and it is why a Marketplace channel behaves nothing like your webshop even with identical products in it.

Two more worth flagging. Tax disappears: PrestaShop resolves tax through rule groups by destination, while Marketplace takes one gross number, so you decide what the buyer sees rather than having it computed. And multi-store has no counterpart — if you run several PrestaShop shops from one installation, choose which one’s prices and stock are authoritative for Marketplace before you publish, not after.

Combinations, and the multiplication problem

PrestaShop combinations are real variant entities: each has its own reference, its own stock row, its own price impact and often its own images. Marketplace has no variants whatsoever. One listing is one item.

So a product with five colours and six sizes is not one Marketplace listing. It is thirty. And because Marketplace listings are created individually and surfaced by proximity, thirty near-identical listings from one seller is both a large amount of work and a poor experience for a local browser scrolling past the same jacket in six sizes.

The sensible approaches, in order of how often they are right:

• List selectively. Push your best sellers, your highest-margin lines and anything you want cleared locally — not the catalogue. This is the correct answer for most merchants.
• List one representative combination per product, with the variations described in the text, and handle the specifics in the message thread. Marketplace is a conversational channel; buyers expect to ask.
• List every combination only where each is genuinely a distinct desirable item rather than a size run.

Note also that stock in PrestaShop is tracked per product and per combination and per shop. Whichever approach you take, the quantity that governs whether a Marketplace listing should exist is the combination-level one for the shop you nominated — not the product-level total, which can be comfortably positive while the specific variant you listed is gone.

Getting listings approved and keeping the account

Meta’s Commerce Policies are the rulebook, and they are stricter than most merchants expect. They set out 24 prohibited content categories and four restricted ones requiring approval, and Meta enforces them against Marketplace posts by removing violating content globally rather than regionally. Digital goods are explicitly out: commerce content may not promote buying, selling or trading downloadable digital content, digital subscriptions or digital accounts.

Read the prohibited list against your own catalogue before you connect anything. Merchants in supplements, vaping, medical devices, weapons-adjacent outdoor equipment, alcohol and cosmetics with health claims routinely find that a slice of a perfectly lawful catalogue is not permitted on Meta’s surfaces.

Rejections and account restrictions are the dominant seller complaint about Marketplace, and Meta publishes a remediation path for them. Restrictions range from losing Marketplace access temporarily to a full commerce ban, and are commonly triggered by buyer or seller reports, by activity that looks automated, and by payment or identity problems. The relevant behaviours for a merchant crosslisting a catalogue are the obvious ones: publish at a human pace rather than in a burst, do not relist identical items repeatedly, and keep the account you are listing from a real, established one.

One genuine gap in the other direction: Meta’s Commerce Policies set no image resolution or description formatting requirements. Compared with every other channel, Marketplace asks remarkably little of your product data — which is why the constraints that bite here are policy and geography rather than field validation.

What syncs and what does not

Sold-out protection is the feature that makes this pair safe to run, and specifically because of the invisibility problem. A Marketplace sale in Europe is a cash handover Meta never sees, so nothing will ever report it to you. Sell an item on your PrestaShop store and FLUF pulls the Marketplace listing before somebody drives over for it. The reverse direction has a limit you should understand: because Meta never observes the sale, you have to mark it sold — do it on your phone at the handover, and FLUF propagates it everywhere else. It cannot know on its own.

Order sync runs from PrestaShop into FLUF and not from Marketplace, for the same reason. Relisting and offer management are not available on either channel here.

Crosslisting and inventory sync are on every FLUF plan; relisting, offer management and smart pricing are included from Growth (£19 a month) upwards. See the plans — 7 days for £1, then from £9/month, then plans from £9 a month.

Sources and verification

Every behaviour, policy and figure below was checked against a primary source on 5 September 2026, and Meta’s geo-gated pages were observed from Europe.

• PrestaShop guidance on enabling Webservice access.
• the PrestaShop 9 Admin API and the 9.1.5 release notes for the current version and support position.
• PrestaShop’s own homepage for the 250,000-merchant claim, against Store Leads’ PrestaShop report for 149,980 live stores, the year-on-year decline and the country distribution; Capterra reviews for the paid-modules criticism.
• the ps_facebook repository for the module’s version, commit activity and Pixel-and-catalogue scope.
• Meta on Shops and website checkout for the September 2025 change and the discontinuation of post-purchase management in Commerce Manager.
• Meta’s selling-with-delivery help article and its companion, both of which return the location-unavailable message to European visitors.
• Meta’s Commerce Policies for the 24 prohibited and four restricted categories, the digital-goods exclusion and global removal; Meta’s page on restricted commerce accounts for the remediation path.
• Meta on creating a Marketplace listing for the manual, one-at-a-time flow; Meta on catalogue eligibility for the inventory-type restrictions.

Related guides

• Sell on PrestaShop — the complete seller guide
• Sell on Facebook Marketplace — the complete seller guide
• Crosslist from PrestaShop to Shopify
• Crosslist from PrestaShop to Vinted
• All marketplace guides
• All crosslisting routes