Maropost AI Chatbot: Add a Shopping Agent

Yes, you can add an AI assistant to a Neto store through its Custom Scripts settings. shoppa is an AI shopping agent that helps customers find, compare and buy products in the chat. Connect your catalogue and store documents during onboarding, then add shoppa’s two-line embed to your storefront.

The script displays the agent. Catalogue updates and customer-specific prices need their own setup, especially if you sell wholesale alongside retail. The catalogue-to-agent process explains the shared steps, and the platform integration guides cover other storefronts.

Neto is Now Maropost Commerce Cloud

Neto has been known as Maropost Commerce Cloud, and Maropost’s developer documentation still calls the platform Neto by Maropost. That explains why your established store, help articles and theme files can still carry the Neto name.

Use the settings for your Neto storefront when following this guide. Maropost has several products, so a guide to another Maropost platform doesn’t necessarily describe your store’s controls. The Neto developer documentation identifies the platform covered here.

Adding the Script to Your Maropost Theme

Add shoppa’s supplied two-line embed through Custom Scripts in your Neto control panel. This route lets you install it without choosing or editing a theme footer file.

1. Open Settings & tools, then All settings & tools.
2. Select Custom Scripts and create a new script.
3. Give the script a recognisable name, such as shoppa.
4. Paste both supplied script tags into Page Footer, keeping their order and your own retailer details.
5. Complete the email-token verification using Send Token Now and Verify Token when prompted.
6. Save the script, then open your storefront to check that the agent appears.

Saving makes a Custom Script active on the webstore. Maropost’s custom-script instructions place Page Footer code before the closing body tag, except on purchase confirmation. That page has a separate script area. Avoid installing a second copy through the theme as well.

Use the exact embed supplied for your store. Keep the two tags together: the first loads shoppa and the second starts it. Test your existing checkout after adding the script. If the script disrupts it, mark the Custom Script inactive while you resolve the conflict.

Catalogue and Policy Data

Your Maropost catalogue connection is set up with shoppa during onboarding. Product data reaches the agent separately from the storefront script. Installing the embed alone doesn’t copy your products or establish an update schedule.

Map each sellable product and variant to its correct identifier. Include product descriptions, prices and stock, with the attributes customers use to choose. For a kit, keep the kit’s selling details distinct from those of its components. Agree how changed prices and stock reach shoppa before switching the agent on for customers.

Add your shipping and returns content as store documents in shoppa’s workspace. Include freight restrictions, collection rules and return exceptions that affect your range. The agent answers from your catalogue and documents, so an unwritten oversize-freight rule can’t supply the answer a customer needs.

Limits on Maropost

The storefront script places shoppa on your site, but it doesn’t grant access to private customer data or determine wholesale prices. Treat customer permissions and price groups as separate parts of the connection.

For business-to-business (B2B) sales, map your customer groups and their permitted prices during onboarding. Maropost’s theme documentation distinguishes the signed-in customer’s group from the visitor group. Keep restricted price lists out of a public catalogue, and test a retail visitor separately from each wholesale group.

shoppa supports basket actions, payment in the chat and order support. Include these workflows in the store connection, alongside the catalogue. A displayed widget alone doesn’t establish how an existing Maropost basket or order is connected.

shoppa uses your own catalogue and documents for answers. It doesn’t search the open web for a supplier’s specifications or delivery promises absent from your store data.

Checks After Going Live

Check the live agent against the Maropost workflows your customers actually use. Include unusual products and customer groups, as well as a straightforward retail purchase.

• Ask about a kit and its components. Confirm that the recommendation matches the item sold and its price.
• Choose a variant, then refine its colour or size in the conversation. Check the selected variant through basket and payment.
• Ask about an item held across warehouses. Compare the answer with the stock available to fulfil that customer’s order.
• Ask a freight question involving a bulky item or a restricted destination. Compare the answer with your store’s delivery rules.
• Use an order number to request status. For signed-in customers, check that the order belongs to the correct account.
• Compare a signed-out retail price with a signed-in wholesale price. Check that a visitor can’t obtain restricted pricing by asking for it.

Repeat the relevant check after a catalogue update, policy change or theme replacement. If the answer differs from your store, correct the connected data or permissions before directing more customers to that workflow.