Our Sydney eCommerce chatbot development covers product knowledge architecture, conversational design, platform integration, and optimisation. Product knowledge architecture (weeks 1-2): making the chatbot understand your catalogue. The foundation: connecting the LLM to your actual product data — not training a model (impractical for changing inventory) but building a retrieval system that gives the LLM access to current product information. Product data pipeline: extracting product information from Shopify/WooCommerce/BigCommerce — titles, descriptions, prices, variants, images, categories, tags, metafields/custom attributes, inventory levels. This data: enriched with additional context — product relationships ("goes well with"), use cases ("ideal for"), and brand-specific language. Vector database: product data embedded and stored in a vector database (Pinecone or Weaviate) — enabling semantic search. When a customer says "something warm and cosy for winter evenings at home," the vector search finds loungewear, knitwear, and blankets — even if those products never use the words "warm," "cosy," or "winter" in their titles. Real-time sync: inventory and pricing changes reflected in the chatbot's knowledge within minutes — not hours or days. A webhook-based sync: product updated in Shopify → webhook triggers → vector database updated → chatbot immediately aware of the change. Out-of-stock handling: the chatbot never recommending products that are out of stock. When a previously available product sells out: the chatbot acknowledges the change and suggests alternatives. Conversational design (week 2-3): designing how the chatbot communicates. Brand voice: every retailer has a distinct communication style. A luxury fashion brand communicates differently from a surf shop. We design the chatbot's personality to match — tone, vocabulary, formality level, and even humour style. System prompt engineering: crafting detailed instructions that tell the LLM how to behave — "You are a shopping assistant for [Brand]. Your tone is friendly and knowledgeable, like a favourite salesperson who remembers your preferences. You recommend products from our catalogue only. If a customer asks about products we don't carry, acknowledge what they're looking for and suggest the closest alternative from our range." Conversation flows: designing the key interaction patterns — product discovery (open-ended — "I'm looking for a gift for my mum"), product comparison ("what's the difference between these two face serums?"), order support ("where's my order?"), returns and exchanges ("can I return this?"), and complaint handling ("the product I received is damaged"). Each flow: designed with natural language variations, edge cases, and escalation triggers (when should the chatbot hand off to a human?). Australian language handling: the chatbot understanding Australian English — sizing (Australian sizes for clothing and shoes, not US), terminology (thongs = sandals/flip-flops, not underwear; jumper = sweater; runners = sneakers), currency (always AUD, displayed as A$ or $), shipping context (Australian domestic shipping, international shipping from Australia, and the expectation of free shipping over A$100 that most Australian retailers offer). Platform integration (weeks 3-5): connecting the chatbot to your eCommerce stack. Shopify integration: Storefront API (product data, collection data, inventory), Admin API (order lookup, customer data), and cart integration (the chatbot adding products to the customer's cart — not just recommending products but completing the action). The add-to-cart flow: customer says "I'll take the blue one in medium" → chatbot identifies the correct variant → adds to cart via Storefront API → presents cart summary with "proceed to checkout" link. WooCommerce integration: REST API (products, orders, customers), cart session management (adding to the WordPress session cart from the chatbot), and webhook integration (order status updates triggering proactive chatbot messages). Order tracking integration: connecting to shipping providers (Australia Post, Sendle, StarTrack, CouriersPlease) — the chatbot pulling real-time tracking information when a customer asks "where's my order?" Customer identification: for logged-in customers, the chatbot accessing their purchase history, preferences, and loyalty status. "You bought this moisturiser 6 weeks ago — would you like to reorder? I can see it's still in stock at the same price." Widget deployment: the chatbot widget embedded on the retailer's website — bottom-right floating button (standard position), customised to match the site's design (colours, fonts, logo). Mobile-optimised: full-screen chat interface on mobile devices, with touch-friendly interaction elements. Optimisation (ongoing): measuring and improving performance. Conversation analytics: every interaction tracked — questions asked, products recommended, products added to cart, conversations that led to purchase, conversations that led to support escalation. Key metrics: chatbot conversion rate (percentage of chatbot conversations resulting in purchase — target: 8-15%, depending on product category), deflection rate (percentage of support queries resolved without human intervention — target: 60-75%), customer satisfaction (post-conversation rating — target: 4.2+/5), and response accuracy (percentage of product recommendations that match the customer's stated need — measured by human review of sample conversations — target: 85%+). Prompt refinement: using conversation data to improve chatbot behaviour — identifying common questions where the chatbot performs poorly, refining prompts to handle those cases, and A/B testing different approaches. Product knowledge gaps: identifying products that the chatbot struggles to recommend accurately — often because product descriptions lack the information needed for semantic matching. Feeding this back to the merchandising team to improve product data quality.