[Digital commerce & conversion]() / [Use cases]() / [Project baskets]() [How it works]() [What you get]() [Scope]() [Start a review]() [Digital commerce & conversion]()[Guidance]() # Turn “what do I need?” into a complete basket. A shopper describes the project, and gets a basket that’s complete, in stock and theirs to edit. [Start with a conversion review]() [How it works]() Basket · three-day hike Edited by the shopper Item Why it’s here Status Merino crew Base layer for cold nights In stock Canvas field jacket Outer layer. Olive M has 4 days left Navy M offered Trail pant Days on the trail and camp In stock Socks Left out of the first list Added The basket the shopper edits. Every line is checked for size and stock. ## Sound familiar? - Shoppers arrive with a goal, and the site offers a product grid. - Customers buy the jacket and forget the base layer. - Someone on support builds the list by hand. A shopper who can’t work out what they need buys part of it, or goes to wherever offers the whole list. ## What changes. ShowTodayWith the engine Starting point A product the shopper already knows The project they’re trying to finish The list Pieces found one at a time A basket built from the goal, and editable Gaps Found after the order Flagged before checkout, with a reason Judging Add-to-cart clicks Complete baskets that stay sold ## How it works. 5 steps, 4 stages. - AI**1** - Rules and automation**3** - Your team**1** - Approval 1. 1 Ask 1. AI ### Turn the goal into a list Takes a sentence, a photo or a rough list, and asks about what’s missing: weather, length, who it’s for. 2. 2 Build 1. Rules and automation ### Choose valid items Sizes, variants and stock decide what can be offered. Nothing is substituted silently. - Shopify 3. 3 Check 1. Rules and automation ### Check for what’s missing Companion items your merchandisers marked as needed are flagged before checkout. 2. Your team Approval ### Set the project rules Merchandisers define the projects, the pairings and what counts as complete. 4. 4 Learn 1. Rules and automation ### Read the baskets Complete baskets, edits and returns by project, in one view. - Google Analytics Edits and returns improve the next list ## What you get. Real work, every week. I’m doing a three-day hike in October. The nights get cold, and I’ll carry a pack. What do I need? For cold nights: a merino base layer, the Canvas field jacket and trail pants, plus socks, which most lists skip. The jacket isn’t waterproof, so if rain is likely you’ll want a shell from somewhere else. After two questions on cold and pack · from Fernway’s product facts · stock checked The conversation that built it, and what it says about the limits. Basket checks - Every item in the right size - Nothing sold out offered as ready - Required companions flagged - The shopper can remove or swap any line The checks that run on every basket before the shopper sees it. ## How you’ll know it’s working. 1. Complete baskets Baskets with everything the project needs, not the most items. 2. Edits shoppers make Shows where the list was wrong or too long. 3. Contribution after returns A bigger basket only helps if it stays sold. Baselines agreed before we build. ## Works with what you have. Commerce - Shopify Support - Gorgias Measurement - Google Analytics We configure first Shopify’s bundles and collections cover fixed kits. We start there, and build only where the list depends on the shopper’s goal. We build when Needs differ by shopper, and a fixed bundle would be wrong half the time. ## What a first build includes. Built in your accounts, around your team. Scope, fee and baseline agreed before we start. 1. 1 Design 2. 2 Build 3. 3 Run it, or hand it over [Start with a review]() [Scope this build]() ### We build - A project map: goals, items and required pairings - A basket builder that asks what’s missing - Stock, size and variant checks - A readout on complete baskets and returns ### We start from - Product catalog and stock - Sales and support questions about projects - Merchandising rules for pairings ### From your team Owner Head of ecommerce, with merchandising Involves - Ecommerce - Merchandising - Customer service - Engineering ## Questions teams ask. Is this just a bundle? A bundle is fixed. A project basket starts from what the shopper is trying to do and changes with their answers. Fixed kits still make sense where every shopper needs the same thing. What if the assistant leaves out something important? Merchandisers define what each project requires, and rules check every basket against it. Anything the assistant can’t be sure of is flagged for the shopper, not guessed. Who owns it once it’s running? You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your head of ecommerce, with merchandising. We can keep running it with you, or step back. How do we start? Usually with a conversion review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly. ## Part of your conversion engine. One of 14 use cases, in 5 parts. [See the whole conversion engine]() 1. [Evidence & decisions **2**]() 2. [Search & discovery **2**]() 3. [Guidance **4**]() 4. [Cart & checkout **4**]() 5. [Releases **2**]() In guidance - [**Guided shopping**Build a shopping assistant that helps customers choose]() - [**Product page answers**Answer the buying questions your product pages leave open]() - [**Size and fit**Give shoppers size confidence that holds after delivery]() - **Project baskets**You’re here Works with - [**Cart add-ons**Offer add-ons that add profit]() ## Help shoppers finish the project. Start with a conversion review. [Start with a conversion review]() [**Talk it through first**15 minutes]() We reply within one business day. --- Source: [https://www.thekeating.co/use-cases/project-baskets/]() [Contact Keating & Co](mailto:nelson@thekeating.co) · [Agent guidance](https://www.thekeating.co/llms.txt)