All articles

Neuwon for WooCommerce: preparing your AI chatbot for launch

Quick answer: Neuwon's WooCommerce chatbot helps shoppers find and compare products using the store's own data, answers questions from agreed guidance, and can collect contact or quote requests for the merchant. The WooCommerce plugin was released on 23 October 2026. Prepare the rollout by choosing sources, reviewing product information and checking answers in a private preview before publication.

Developed by JR Soft, Neuwon is available for WooCommerce and Magento / Adobe Commerce. It also works on ordinary websites, while Shopify is in development. This guide focuses on preparing the WooCommerce integration: what to gather, what to check and how to decide whether your setup is ready for shoppers. For the other available ecommerce platform, see the Magento / Adobe Commerce guide.

Start with the questions your shoppers ask

Choose a small set of buying situations where customers currently need help. They might be comparing two products, choosing a size, checking a specification or looking for instructions. These questions give the onboarding process a useful scope.

For example, “Which of these would fit a small space?” illustrates a possible question; it does not promise that every catalogue contains the answer. The assistant needs dimensions and relevant product facts to make a supported comparison. If those facts are missing, improve the source or agree how customer service will handle the uncertainty.

Write down the expected answer and its source for each test. That helps you assess accuracy rather than fluency alone. The broader ecommerce chatbot overview explains the purpose; your pilot turns it into questions that matter in your particular store.

Review product information and variations

The WooCommerce plugin provides a product-data connection to Neuwon. Its data structures include names, descriptions, categories, images, prices, product links and public attributes. Variation choices and availability information are also represented. The sources and attributes used are agreed for each store.

Focus your review on the facts customers need to choose. Are sizes, materials and dimensions consistent? Can someone understand an attribute without knowing an internal abbreviation? Are differences between variations clear? A hidden internal field should not be assumed to be a public answer source.

You do not need to rewrite the entire catalogue for an assistant. Correct missing facts and contradictions first. The product page remains an important place for shoppers to inspect the recommendation and make their own decision.

Ask someone who knows the range to review exceptions. A dimension might describe the packaging rather than the product, or the same size label might mean different things across collections. Resolving those details is more useful than adding general promotional text that does not help a shopper choose.

Keep availability separate from delivery promises

The integration carries stock status and stock quantity where WooCommerce manages it. That can support availability answers, but a stock figure alone does not establish handling time, transit time or an arrival date.

Prepare delivery guidance alongside product information. Explain what “in stock” means for your operation, how backorders are described and which exceptions customer service must confirm. Do not approve a precise delivery promise when the supporting information is absent.

In the preview, check a product with several sizes or options. Confirm that the answer refers to the variation the shopper asked about. Treat availability evidence and a delivery commitment as separate items in your acceptance checklist.

Select guidance and PDF documents deliberately

Agreed guidance, FAQ content and PDF documents can complement the catalogue. The plugin supports document links in explicitly selected public product attributes. This does not mean every WordPress file or downloadable product automatically becomes answer material.

Start with public instructions that address a real customer question, such as an installation or user guide. Check its version, language and product association. A readable document can still be an unsuitable source if it describes an older model.

Keep paid downloads, internal documents and customer-specific files separate. Agree the permitted document sources during onboarding and confirm that you have the right to use the material. Accurate source selection matters more than the number of files connected.

Decide how contact and quote requests will be handled

Neuwon can collect contact details and quote requests under the agreed operating model. This can help when a shopper needs a personal answer or wants a quotation for a larger quantity. The assistant does not need to invent a special price to help the enquiry move forward.

Choose who receives requests and which details they need to respond. Ordinary product advice may not need contact details at all. When someone requests a reply, the purpose of collecting their information and the next step should be understandable.

Test this workflow using agreed test details. Check that the question is clear to the recipient, relevant product information is included and someone owns the follow-up. A confirmation in the chat window is only one part of the process.

Move from installation to a private preview

The WooCommerce connection uses a WordPress plugin. Onboarding includes checking the store environment, agreeing the connection to Neuwon and selecting the material to use. Theme and extension compatibility should be assessed in the actual store; platform support alone does not prove every possible combination works.

A private preview lets you check the assistant against your own product and availability data before shoppers see it. Include these situations in the review:

  • A direct question about a known product and a key attribute.
  • A search based on a need without naming a product.
  • A comparison where one important fact is missing.
  • An availability question about a specific variation.
  • A question answered from an approved guide, followed by an uncertain enquiry.

Review the chat window on a phone as well. Check readability, product links and whether the window obstructs essential store controls. Publication follows the controlled preview and merchant approval. Installing the plugin successfully is an earlier milestone, not the content acceptance decision.

Keep a short record of each question, observed answer, source and correction. After improving a source, repeat the buying situation and try a slightly different wording. This helps distinguish a missing product fact from a presentation issue.

Assign ownership before launch

Name the person responsible for catalogue and guidance updates. Agree how a changed delivery policy or retired document will be reflected in the assistant's sources. An assistant still depends on the merchant maintaining reliable information.

Discuss customer information and data handling at the same time. Read the chatbot privacy and EU AI Act guide before approval, and check the current service terms and scope through the pricing page and onboarding discussion. Clear sources, responsibilities and acceptance checks make the launch easier to evaluate.

Frequently asked questions

Is the Neuwon WooCommerce plugin available?

Yes. It was released on 23 October 2026. The onboarding scope, selected information and suitability of the store environment are checked for each merchant before customer-facing publication.

What information does the chatbot need?

Start with your store's product information and agreed service guidance. Review attributes that affect buying decisions, variation choices and availability. PDF guides are selected separately as part of the agreed material.

Can the assistant compare products?

Yes, comparisons can use store product data and the shopper's needs. The relevant attributes must be present in the sources. Missing compatibility information or another decisive fact should not be treated as permission to guess.

Is all WordPress content included automatically?

No. Sources are agreed explicitly. Public product data, selected document links and approved guidance are kept distinct from internal files and material that is not intended for shopper answers.

Can I try the assistant before publishing it?

Yes. A private preview lets you review answers and product guidance using your store's material. The merchant approves the prepared setup before the assistant is published to customers.

Prepare your store's onboarding

Explore the WooCommerce integration and contact JR Soft. Share your store address, main product groups and the questions customers need help with. These provide a practical starting point for agreeing sources, the preview and the next steps.