Meta Shops Checkout URL Support for Facebook & Instagram Shopping

Abby Thomas

We currently use Neto by Maropost as our ecommerce platform and the existing Facebook Catalogue feed successfully syncs our products into Meta Commerce Manager.

However, Meta now requires merchants to provide a compatible Checkout URL in Commerce Manager in order to enable Facebook and Instagram Shops/product tagging.

Neto already supports direct checkout/cart URLs, but the current Neto URL structure does not natively accept the parameter format used by Meta Shops.

The missing functionality is a Neto endpoint that can receive Meta’s product and quantity parameters, for example:

?products=PRODUCT_ID:QTY,PRODUCT_ID:QTY

and then translate those values into a valid Neto cart/checkout session.

Ideally, Neto would provide an official Meta-compatible Checkout URL endpoint that:

* accepts multiple Meta product IDs and quantities;
* maps Meta catalogue IDs to Neto SKUs;
* adds the correct products and quantities to the Neto cart;
* redirects the customer into the standard Neto checkout;
* supports optional coupon/promotion parameters where relevant;
* preserves tracking parameters such as UTM values and fbclid;
* works with the existing Neto Facebook Catalogue integration;
* is documented as the recommended Checkout URL for Facebook and Instagram Shops.

This is currently preventing merchants using Neto from fully enabling Instagram as a Shop sales channel and from using product tagging correctly, despite the product catalogue itself syncing successfully.

From a merchant perspective, this appears to be a relatively small compatibility layer between Meta’s checkout URL format and Neto’s existing cart URL functionality, but it is now important for continued Meta Commerce support.

It would be very useful if Maropost could prioritise this as part of the Neto ecommerce roadmap.

Business impact:
Without this support, Neto merchants can maintain a Meta catalogue but cannot fully participate in the current Facebook/Instagram Shops checkout flow without custom development. This reduces the usefulness of the existing Facebook Catalogue integration and creates friction for merchants relying on Instagram product tagging and social commerce.

adrian

Hi @Abby Thomas

Good news, most of this already works in Neto today. It just doesn't speak Meta's URL format. It can be fixed with a bit of custom code.

An official documented endpoint would still be better than everyone rolling their own, but merchants aren't blocked in the meantime.

The cart already accepts multiple products with quantities, a coupon code, and can drop the customer straight into checkout: /_mycart?multi=2&sku0=ABC&qty0=1&sku1=XYZ&qty1=2&fn=payment

The fix is to point Meta's Checkout URL at a custom page on your own store (/meta-checkout or similar) and let that page translate Meta's format into the URL above and redirect.

Two things that page needs to handle: the cart adds to whatever's already in it rather than starting fresh, and if any item is out of stock Neto bounces you back from checkout with an error.

I've built and tested a handler that does this. Send me a DM if you'd like some help getting this set up.