Open your Lulu store: from signup to going live
Create your account, choose a package and pay for the first billing cycle, add a theme and apps, then go live.
Illustrated guide: lulu.us.com/help/open-your-shopwise-store
Before you startOpening a store means choosing a package and paying for its first billing cycle; there is no free tier, and your store is created as soon as that payment goes through. While you build, your shop is password-protected ("In development"): visitors see a coming-soon page until you go live in the last step. This walkthrough was verified on a fresh store; the screenshots come from that run.
1. Choose a package and create your account
Go to Pricing and click "Choose Basic", "Choose Grow" or "Choose Advanced", or click "Get started" (Plus is a custom agreement: use "Talk about Plus"). The signup form has three steps: 01 Account, 02 Your store and 03 Package. On the first step enter your email and a password of 8 to 72 characters, then click "Continue", or use "Continue with Google". Nothing is charged at this step.
2. Name your store, choose your package and pay
Enter your store name and a store address made of 3 to 40 lowercase letters, numbers and hyphens. The page checks availability as you type; wait for "This store address is available", then click "Continue". On step 03 Package pick Monthly or Yearly and your package, click "Continue to payment ↗" and pay for the first billing cycle on the secure payment page. Your store is created once the payment goes through; no payment means no store.
3. Land in your admin
Your new admin opens at admin.lulu.us.com/store/your-address, and a welcome email with an "Open your admin" button, your store's web address and the storefront password arrives. Your shop lives at your-address.lulu.us.com. The Home page shows a "Set up your store" guide that ends with "Go live"; the sidebar holds Products, Orders, Online Store, Apps and Settings.
4. Check your package under Settings > Billing
Open Settings > Billing. The top card shows your package, its renewal date and the platform transaction fee. To move to another package later, use "Upgrade" or "Downgrade" under "Change package": upgrading applies straight away and charges only the difference for the days left in the cycle; downgrading takes effect on your renewal date.
- Full details, including how renewals work: Pay for your package (linked below).
5. Add a theme
In the admin open Online Store and click "Browse themes" to open the Theme Store inside your admin ("Visit Theme Store" opens the public Theme Store site). Open a theme and click "Try theme". It is added to your drafts; click "Edit theme" to customise it and "Publish" when it is ready. Free themes publish immediately. Premium themes can be tried and edited free; a premium draft shows "Buy to publish" with its price, and you pay once when you publish.
- Full details: Try, buy and publish a theme (linked below).
6. Add apps
In the sidebar click "Apps", then "Lulu App Store" (while no app is installed the sidebar also shows "Add apps"), or browse apps.lulu.us.com. Open an app and click "Install". A confirmation shows what the app does, which data it can read or edit and what it costs before anything is added. Then choose a plan under Pricing: free-trial lengths vary by app and are shown on each plan. A free plan marked "Development stores only" is free only until your store goes live. A paid plan starts the app's normal free trial, then bills, whether or not your store is live.
- Full details: Install apps and pay for app plans (linked below).
7. Go live
Add products under Products > Add product. Set up Settings > Payments with your own gateway (PayHere, Koko, Mintpay, WebXPay, Stripe, PayPal or cash on delivery) and Settings > Shipping and delivery. Connect a domain under Settings > Domains, or keep your-address.lulu.us.com. Finally open Home > Go live (also reachable from Online Store > Preferences): its checklist confirms your package, paid apps and theme are settled and a payment method works, charges any app whose payment is due (an app still in its free trial is not charged), and then opens your store to everyone.
- Products > Add product
- Settings > Payments and Settings > Shipping and delivery
- Settings > Domains (optional)
- Home > Go live
Completion checklist
- You can sign in to admin.lulu.us.com/store/your-address.
- Settings > Billing shows your package as Active with a renewal date.
- A theme is Live under Online Store and at least one product is published.
- Payments and shipping are configured and the Go live page says your store is open.
Troubleshooting
The store address I want is taken or reserved.
Choose another address; it only affects your free lulu.us.com link. You can connect your own domain later under Settings > Domains.
The payment window says the payment could not start, or closes without a result.
Nothing was charged and your current package, theme or app tier stays exactly as it was. Try again in a few minutes. If it keeps failing, the platform's card payment provider is not live yet for this region: contact support with your store address and what you were paying for, and the team will complete the activation with you.
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Get to know your Lulu admin
Find the pages you use to manage your store, products, orders, and settings.
Illustrated guide: lulu.us.com/help/get-to-know-your-admin
Before you startSign in to your store. The examples below use a demonstration account and sample orders.
1. Start at Home
The Home page summarizes sales, orders, average order value, and unfulfilled orders for the selected period. Use the period selector at the top right to change the view. Sample figures in this guide are not business performance claims.
2. Use the navigation
Choose Products to manage your catalog, Orders to work on purchases, Online Store for themes and pages, and Analytics for reports. Some navigation groups expand to show additional pages. On a phone, open the menu first.
3. Find store-wide settings
Select Settings at the bottom of the sidebar. The settings menu includes Payments, Shipping and delivery, Domains, and Users and permissions. What you can change depends on your staff permissions. On a computer, Settings opens over the page and the main menu shrinks to a strip of icons on the left — hover an icon to see its name, or click it to leave Settings and go straight to that section. Most settings forms ask before you leave if you have unsaved changes, so save first.
Completion checklist
- Confirm the correct store name in the admin before making changes.
- Review the saved result in your storefront or admin.
- Complete the launch checklist before sharing your store.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Add your first product
Create a product with the information your customers need to make a choice.
Illustrated guide: lulu.us.com/help/add-your-first-product
Before you startPrepare a title, description, product photos, price, stock quantity, and any variant choices.
1. Open Products
In your admin, select Products. The All, Active, Draft, and Archived tabs help organize the catalog. Select Add product in the top right.
2. Write the title and description
Enter a clear product title and accurate description. Add details such as materials, dimensions, care, or compatibility. If you use Write with Wise AI, review the generated text before saving.
3. Add media, price, and stock
Use the Media controls to upload images or add supported URLs. Continue down the page to set pricing, inventory, and variants where needed. Enter the real selling price and stock values; example products in this guide are only demonstration data.
4. Choose status and save
Use Draft while you are preparing the product. Review the publishing setting and save when the content is ready. Preview an active product on the storefront to check images, variants, and the add-to-cart flow.
Completion checklist
- Check each variant’s title, SKU, price, and availability.
- Preview the product or collection on desktop and mobile.
- Keep unfinished products in Draft until their details are ready.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
The product is missing from my store.
Confirm the product was saved with the intended status and storefront availability. If customers browse through a collection or menu, check that the product is reachable there too.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Organize and find your products
Use product status, search, filters, and collections to keep your catalog manageable.
Illustrated guide: lulu.us.com/help/organize-your-product-catalog
Before you startYou need permission to view products. Editing, importing, and exporting can require additional access.
1. Choose the right status view
Open Products and use All, Active, Draft, or Archived. Keep unfinished products in Draft so preparation work is easy to find.
2. Search and filter
Use Search products to find a title. Add filter lets you narrow the list using the available fields. Sort changes the ordering of the results. Clear filters if an expected product is missing.
3. Organize the storefront
Use Collections under Products to group items in a way customers understand. Review product type, vendor, and tags for consistent naming. Check collections from the storefront before promoting them.
4. Import carefully
Use Import for supported product data and review the required file format. Start with a small test batch, check variants and images, then import the rest. Export a backup before a large catalog change.
Completion checklist
- Check each variant’s title, SKU, price, and availability.
- Preview the product or collection on desktop and mobile.
- Keep unfinished products in Draft until their details are ready.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Choose and preview a theme
Find your live theme, work on a draft, and check the result before publishing.
Illustrated guide: lulu.us.com/help/choose-and-preview-a-theme
Before you startHave your brand assets ready. A development store can remain password-protected while you build.
1. Open Online Store
Select Online Store in your admin. The Themes tab shows your current theme with a Live badge and your draft themes below it.
2. Customize or prepare a draft
Select Customize on the current theme, or Edit theme on a draft. Use a draft when you want to prepare changes before making them visible in the live theme. Work through the available sections, content, and styles.
3. Review desktop and phone layouts
Preview your storefront, then check navigation, product pages, images, and calls to action at different widths. Confirm that content is readable without horizontal scrolling.
4. Publish deliberately
Review the theme actions and choose Publish for the draft you want customers to see. Publishing a theme is separate from removing a development-store password or activating paid services. Confirm all launch requirements before sharing your store widely.
Completion checklist
- Confirm you are editing the intended store and theme.
- Test links and layout in a separate storefront tab.
- Check the same pages on a phone before announcing the change.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Connect an existing domain
Point a domain you already own to your Lulu storefront.
Illustrated guide: lulu.us.com/help/connect-your-domain
Before you startYou need access to the domain’s DNS settings at your registrar. Keep a record of existing DNS records before making changes.
1. Open Domains
Go to Settings, then Domains. Your managed lulu.us.com address appears here. Choose Connect existing domain to begin.
2. Enter your domain
Enter the domain you want customers to use. Follow the connection instructions shown for your domain. Copy the exact record names and values from the setup rather than using values from a screenshot.
3. Update DNS at your registrar
Add or update only the records requested by the setup. Do not remove unrelated email records. DNS propagation and certificate provisioning can take time; review the connection status before switching your main address.
4. Verify the customer journey
Open the domain in a private browser window and check the storefront and checkout. Keep your previous setup available until you have confirmed the new address works. Registration and renewal charges remain separate from domain connection.
Completion checklist
- Confirm you are editing the intended store and theme.
- Test links and layout in a separate storefront tab.
- Check the same pages on a phone before announcing the change.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My domain still does not open the store.
Compare the records at your DNS provider with the exact values shown in Lulu. Check for conflicting records on the same hostname. DNS changes can take time; avoid repeatedly replacing records while a change is being verified.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Connect a payment provider
Find payment settings and prepare your store to accept supported payment methods.
Illustrated guide: lulu.us.com/help/connect-a-payment-provider
Before you startApply for and obtain the merchant account your provider requires. Check country, product, currency, and recurring-payment eligibility.
1. Open Payments
Go to Settings, then Payments. Development stores show a test-payment notice. Test payments do not collect real money.
2. Choose your payment methods
Review the Manual payment methods options if you plan to offer cash on delivery or bank transfer. For an online gateway, select the appropriate provider from Add a payment provider and follow its configuration fields.
3. Connect credentials securely
Use the credentials required by your provider and choose test or live mode carefully. Never paste secret keys into public pages, support screenshots, or email. Save the settings after reviewing them.
4. Test and confirm activation
Test a complete checkout and verify the payment status in Orders. Before accepting real money, confirm store activation, live provider credentials, currency support, and the applicable package and processing fees.
Completion checklist
- Confirm your provider account and store settings are ready.
- Test a supported address and payment method end to end.
- Check the resulting order status before treating an order as paid or shipped.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
The checkout reports a connection or payment error.
Check that the selected provider is activated, its account can accept payments, and the credentials match the intended test or live environment. Review the order and provider dashboard before retrying so you do not charge twice.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Set up shipping and delivery
Review shipping profiles, zones, rates, and delivery options before you launch.
Illustrated guide: lulu.us.com/help/set-up-shipping
Before you startPrepare the destinations you serve, product weights, package information, and the rates or thresholds you want to offer.
1. Open Shipping and delivery
Go to Settings, then Shipping and delivery. The Shipping card brings together profiles, packages, and rates and zones.
2. Review the shipping profile
Open the General profile or the relevant product profile. Check the products and locations assigned to it. Use separate profiles only when your products need different delivery rules.
3. Configure zones and rates
Open Rates and zones to review destinations and available rates. Add the supported fixed, weight, or order-based rules you need, and save changes. Check how any free-shipping threshold interacts with discounts.
4. Check pickup, tracking, and test addresses
Review the additional delivery methods that fit your business. Automatic tracking requires a supported tracking provider. Test checkout with an address inside and outside your delivery zones before launch.
Completion checklist
- Confirm your provider account and store settings are ready.
- Test a supported address and payment method end to end.
- Check the resulting order status before treating an order as paid or shipped.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
A customer sees no delivery option.
Test the same country, region, and postal code. Check whether the products belong to the expected shipping profile and whether the cart meets the rate conditions. Also check pickup or local delivery restrictions if you use them.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Review and fulfill an order
Read payment and fulfillment status before preparing a customer’s order.
Illustrated guide: lulu.us.com/help/review-and-fulfill-orders
Before you startCheck your staff permissions and the store’s fulfillment process. The orders below are manually created demonstration orders, not real purchases.
1. Open the order list
Select Orders in the admin navigation. Review the order number, customer information, totals, and payment and fulfillment statuses. Use the available tabs and filters to focus the queue.
2. Open an order and verify it
Select the order number to review the items, quantities, delivery information, and payment details. A pending payment is different from a paid order. Confirm your store’s policy before shipping an unpaid order.
3. Record fulfillment
Use the fulfillment controls available on the order, choose the quantities being sent, and add carrier and tracking details where applicable. Review the information before saving or sending a customer notification.
4. Handle follow-up from the order
Return to the order to check status, notes, refunds, or returns as your permissions and payment method support them. Reconcile actual provider refunds with the order record.
Completion checklist
- Open the correct order or customer record.
- Check payment and fulfillment separately.
- Review the saved result before sending a customer an update.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
An order is paid but still unfulfilled.
Payment and fulfillment are separate states. Check which items remain unfulfilled and who is responsible for shipping them. Add fulfillment only after the relevant items are ready and the shipment details are correct.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Create a discount code
Set an offer, its eligibility, and its limits before sharing it with customers.
Illustrated guide: lulu.us.com/help/create-a-discount
Before you startDecide the offer type, discount amount, applicable products, start and end dates, and how much margin you can afford.
1. Open Discounts
Select Discounts, then start a new discount. Choose the type that matches your offer. The example shows an Amount off products discount.
2. Set the method and value
Choose Discount code when customers should enter a code, or Automatic discount for a qualifying automatic offer. Enter a code and choose Percentage or Fixed amount as appropriate.
3. Define who and what qualifies
Review eligible products and customers, minimum purchase requirements, usage limits, and combination settings. Set the active dates and check the summary to the side of the form.
4. Save and test
Save the offer, then test a qualifying cart and a non-qualifying cart. Confirm the discount amount, shipping, tax, and any interactions with other offers before sending the code to customers.
Completion checklist
- Check the date range, eligibility rules, or campaign conditions.
- Test using a qualifying product and a non-qualifying example.
- Review the customer-visible result before promoting an offer.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
The discount does not apply.
Check the start and end dates, qualifying products, minimum purchase, customer eligibility, usage limit, and combination settings. Test a cart that meets every rule; a discount should not apply outside those conditions.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Understand your sales overview
Use the Home page and Analytics to answer specific questions about your store.
Illustrated guide: lulu.us.com/help/understand-your-reports
Before you startChoose a clear reporting period. Sample numbers in these screenshots are demonstration data.
1. Review the Home summary
Open Home to see the selected period’s sales, order count, average order value, and unfulfilled orders. The recent orders list gives context behind the summary.
2. Open Analytics
Select Analytics for additional reporting tools. Review the chosen period and use reports that match the question you are trying to answer.
3. Keep definitions in mind
An order total is not the same as a payment-provider settlement. Refunds, pending payments, fees, currency, and reporting time boundaries can affect comparisons. Reconcile using the underlying records.
4. Choose a next step
Use the data to identify a concrete action, such as checking an unfulfilled order, improving a product page, or adjusting stock. Reports support decisions; they do not guarantee a particular business result.
Completion checklist
- Check the date range, eligibility rules, or campaign conditions.
- Test using a qualifying product and a non-qualifying example.
- Review the customer-visible result before promoting an offer.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Install and configure an app
Review an app’s capabilities, plan, and requirements before adding it to your store.
Illustrated guide: lulu.us.com/help/install-and-configure-apps
Before you startUse an account with permission to manage apps. Some tools have separate subscriptions, provider accounts, or theme requirements.
1. Open the App Store
In the admin click Apps, then Lulu App Store (while no app is installed the sidebar also shows Add apps), or browse the public Lulu App Store. Search for the job you want to solve rather than adding tools without a clear need.
2. Review the listing
Read the app description, available features, planned capabilities, required permissions, and setup requirements. Compare plan prices, free-trial lengths and billing terms. A free plan marked "Development stores only" is free only until your store goes live.
3. Install and configure
Install the app for the correct store and complete the setup it provides. If the app changes the storefront, enable its supported app block, section, or embed in your theme.
4. Preview and monitor
Test the experience on phone and desktop. Review usage and costs as traffic grows. Open the app’s specific help guide or use its support link when you need assistance.
Completion checklist
- Review charges, permissions, and connected account requirements.
- Configure the app before expecting it to affect your storefront.
- Preview the result and keep a note of the settings you changed.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Choose a package and understand billing
Compare Basic, Grow, Advanced and Plus, check the whole cost, and know that the first billing cycle is paid during signup.
Illustrated guide: lulu.us.com/help/choose-a-package
Before you startKnow your staff, catalog, location and integration requirements. All package prices are in USD and there is no free package: your store is created only after its first billing cycle is paid. Existing subscriptions follow their current agreement until a change is confirmed.
1. Compare the package matrix
Open the public Pricing page and use the monthly or yearly selector. Basic is $20, Grow $50 and Advanced $290 a month; on yearly billing they cost $17, $45 and $250 a month, paid as one yearly payment of $204, $540 or $3,000. Plus starts at $1,950 a month by agreement with the team. Use Find a feature or Show differences only to narrow the matrix.
2. Check the whole cost
Review the platform transaction fee (Basic 1.5%, Grow 0.8%, Advanced 0.5% of your sales) separately from your payment provider's own processing fee. Include optional app plans, premium themes, domains, messaging, advertising and hardware where applicable.
3. Choose and pay during signup
Click "Choose" on a package (or "Get started"), create your account and name your store. On the last signup step confirm Monthly or Yearly and the package, click "Continue to payment ↗" and pay for the first billing cycle on the secure payment page. Your store is created only after that payment goes through. For Plus, use "Talk about Plus" and agree the terms with the team first.
4. Change your package later
After signup, open Settings > Billing and use "Upgrade" or "Downgrade" under "Change package". Upgrading applies straight away and charges only the difference for the days left in the cycle; downgrading takes effect on your renewal date.
- How renewals are paid: Pay for your package (linked below).
5. Ask about a mismatch
If your admin’s current billing differs from a public package, contact the team before purchasing or switching. Send your store address and the package name, never your card details or account password.
Completion checklist
- Check the store and account you are managing.
- Review the actual terms and currency shown before a paid action.
- Keep the confirmation or contact support if details do not match.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
The amount shown at checkout is different from the pricing guide.
Do not confirm a payment until the amount, currency, billing period, and included services are clear. Send the pricing page and checkout details to the team so they can confirm the correct agreement for your store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Test your store before launching
Work through the customer journey before opening your store to real orders.
Illustrated guide: lulu.us.com/help/test-before-launch
Before you startKeep your store in development while preparing it. Use provider test modes and sample data.
1. Check your theme and navigation
Open Online Store and confirm which theme is live. Preview the home page, collections, product pages, navigation, footer, and contact information on phone and desktop.
2. Check catalog details
Review images, descriptions, prices, variants, and stock. Confirm that unfinished products stay in Draft and that active products can be found through collections or navigation.
3. Test payment and delivery
Check payment test mode, shipping zones, rates, tax settings, and discount behavior. Use realistic sample addresses and test both successful and unsuccessful payment flows where your provider supports them.
4. Confirm the order and launch requirements
Verify the resulting order, notification, and fulfillment process. Before removing development restrictions, confirm your domain, commercial package, live payment credentials, business policies, and readiness to fulfill real orders.
Completion checklist
- Confirm the correct store name in the admin before making changes.
- Review the saved result in your storefront or admin.
- Complete the launch checklist before sharing your store.
Troubleshooting
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
My change is not visible in the storefront.
Confirm the change was saved, then open the correct storefront in a separate tab. Check product status and the published theme. A preview or draft can differ from the live store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Create and organize product collections
Group products into collections and make them easy to browse.
Illustrated guide: lulu.us.com/help/create-product-collections
Before you startPrepare a few products and decide whether you want to choose items manually or use matching conditions.
1. Open Collections
Open Products, then Collections. This page lists your collections and provides search. Select Add collection to begin.
2. Describe the collection
Enter a clear title and a short description. Add an image that represents the range; do not use the image as a substitute for a readable title.
- Use a name customers understand, such as New arrivals or Everyday essentials.
- Check spelling and preview any description formatting.
3. Choose Manual or Smart
Manual collections let you select products individually. Smart collections use conditions to include matching products. Choose the behavior that fits how you maintain your catalog.
- For Manual, use Add products and review the selected items.
- For Smart, use Add condition and inspect which products match.
4. Set presentation and visibility
Choose a sort order and review the Online Store Visible or Hidden setting. A parent collection can organize the hierarchy, but it does not share products between collections.
5. Save and test the collection
Save the collection, then open the storefront. Check its title, image, product order, and product links. Add it to your storefront menu where customers should find it.
Completion checklist
- Check each variant’s title, SKU, price, and availability.
- Preview the product or collection on desktop and mobile.
- Keep unfinished products in Draft until their details are ready.
Troubleshooting
The collection is empty.
For a manual collection, check the selected products. For a smart collection, inspect the matching conditions and product values. Also check whether the products are visible to storefront customers.
The collection exists but customers cannot find it.
Check the collection’s publishing setting and add an appropriate menu link. A saved collection is not necessarily linked from your header or footer.
Review and manage product inventory
Understand your stock view and check the right product, variant, and location.
Illustrated guide: lulu.us.com/help/manage-inventory
Before you startHave your product SKUs and a recent stock count ready. Review connected supplier or inventory syncs before making manual changes.
1. Open Inventory
Under Products, open Inventory. Use the location selector and search to narrow the view before reviewing stock.
2. Identify the right variant
Match the product and SKU to your stock record. Similar product titles can refer to different sizes, colors, or variants. Do not update quantities based on title alone.
3. Read the stock columns
Review Available, Committed, Unavailable, On hand, and Incoming separately. Incoming stock is not the same as stock already available to sell. Investigate differences against orders and stock movements.
4. Apply the intended change
Use the available inventory editing or import workflow for your store. Keep a record of the reason and check the location before saving. For bulk work, export a reference first and try a small sample.
5. Verify stock and storefront behavior
Reload the inventory view and inspect the affected product in the storefront. If quantities change again, check whether an external supplier or inventory integration is the source of truth.
Completion checklist
- Check each variant’s title, SKU, price, and availability.
- Preview the product or collection on desktop and mobile.
- Keep unfinished products in Draft until their details are ready.
Troubleshooting
Available stock differs from the count on the shelf.
Review committed and unavailable units, then confirm the selected location and variant. Check recent orders, adjustments, transfers, and returns before changing the figure.
My manual change is overwritten.
Check connected inventory or supplier syncs. Agree which system should control the quantity and update that source rather than repeatedly editing conflicting values.
Build your storefront navigation
Create menus that help customers find products, collections, and useful information.
Illustrated guide: lulu.us.com/help/build-store-navigation
Before you startPrepare the destination pages or collections before linking to them.
1. Open Content → Menus
Open Content in the admin navigation, then Menus. Choose Create menu to start a new menu or open an existing one.
2. Give the menu a clear purpose
Create a menu for the area where it will appear, such as the main navigation or footer. Use a name your team can recognize.
3. Add useful destinations
Add readable link labels and select the intended destination. Keep your main navigation focused on the paths most customers need.
- Link to collections, products, or information pages that are ready to view.
- Check external addresses carefully before saving them.
4. Connect the menu to your theme
Save the menu and open your theme customization. Select the menu in the relevant header or footer setting where your theme provides it. A newly saved menu does not automatically replace every theme menu.
5. Test every link on a phone
Preview the storefront on desktop and mobile. Open the mobile navigation, follow each link, and check that submenu items are usable with a keyboard as well.
Completion checklist
- Confirm you are editing the intended store and theme.
- Test links and layout in a separate storefront tab.
- Check the same pages on a phone before announcing the change.
Troubleshooting
My menu does not appear.
Confirm it is saved and selected by the published theme’s header or footer. Check the theme preview separately from the live storefront.
A link opens a missing page.
Open the destination directly. Check that the product, collection, or page still exists and is visible, then update the saved menu link.
Find and manage customer records
Find customers, review their purchase history, and maintain useful records.
Illustrated guide: lulu.us.com/help/manage-customer-records
Before you startUse an account with customer access. Only add or import information you are authorized to handle.
1. Open Customers
Use Customers in the admin. Start from All customers or one of the available views, and use search to find the person you need.
2. Check for an existing record
Search the email address before adding a new customer. Compare available identifying details so you do not confuse people with similar names.
3. Add or update the required details
Use Add customer for a new record, or open an existing customer to edit it. Enter the details needed for the task and review any email-subscription preference carefully.
4. Review orders and grouping
Use purchase history and available tags or segments to understand the customer relationship. A customer record alone does not confirm a payment, delivery, or marketing subscription.
5. Save and verify
Save the change and reopen the record to confirm it. Restrict exports to the people who need them and avoid including customer details in public screenshots.
Completion checklist
- Open the correct order or customer record.
- Check payment and fulfillment separately.
- Review the saved result before sending a customer an update.
Troubleshooting
A customer seems to be missing.
Clear search and view filters, confirm the active store, and search using the email used for checkout.
Can I treat all customers as email subscribers?
No. Review the subscription status for the customer and use your approved consent process before including them in marketing.
Add team members and review access
Give staff access to the parts of your store they need.
Illustrated guide: lulu.us.com/help/manage-team-access
Before you startSign in as the owner or an account allowed to manage users. Confirm any staff-seat limits before adding people.
1. Open Users
Open your store’s user-management area. Review the Users, Roles, Collaborators, and Security tabs available to your account.
2. Review the current team
Check who already has access and the role assigned to each person. Confirm the store name before changing anyone’s access.
3. Add the staff member
Choose Add staff, enter the requested identity details, and follow the form’s access setup. Each person should use their own account instead of sharing the owner login.
4. Choose an appropriate role
Use the available roles and permissions to match the person’s work. Keep billing, user management, and sensitive settings limited to people who actually manage them.
5. Check access and review regularly
Have the staff member confirm that the intended pages open. Review access when someone’s role changes or they leave. Treat ownership transfer as a separate, deliberate operation.
- Partners and agencies should not get a staff account. Give them collaborator access from the Collaborators tab instead, and choose what they can do with "Edit access".
Completion checklist
- Check the store and account you are managing.
- Review the actual terms and currency shown before a paid action.
- Keep the confirmation or contact support if details do not match.
Troubleshooting
A team member cannot open a page.
Ask an authorized administrator to check their role and permissions. Also confirm the feature is enabled and available for the store.
The Add staff action is unavailable.
Check your account permissions and package staff limit. Ask the owner to review the store settings or contact support.
Set up dropshipping on Lulu
Plan activation, supplier connections, products, and a test order before launch.
Illustrated guide: lulu.us.com/help/start-dropshipping
Before you startChoose your supplier and markets. Dropshipping requires activation and configuration; creating a Lulu account alone does not activate supplier routing.
1. Check whether dropshipping is enabled
Open Dropshipping in the admin. If you see “Dropshipping isn’t enabled yet,” contact the Lulu team to arrange activation. The screenshot shows this actual state in our demo store. Do not accept supplier-fulfilled orders before setup is complete.
2. Choose the right provider
CJdropshipping and AliExpress provide sourcing connections. Printful and Printify support print-on-demand workflows. Amazon MCF fulfills stock you already own and store with Amazon.
3. Prepare account access
Complete your provider account requirements and arrange its authorized connection with the team. Confirm the correct account, required permissions, and billing arrangements. Do not send API keys in a general support message.
4. Add the supplier after activation
In Dropshipping, choose Add supplier. Enter a recognizable Name, select the Provider and Kind, and review the minimum advertised price option if it applies. Creating this record is only part of the setup; provider authorization and product mapping still need to be completed.
5. Review products and prices
Prepare the products and variants you want to sell. Match supplier items accurately, review your retail prices, and confirm delivery destinations and return expectations.
6. Test the complete order journey
Agree a test procedure with the team and provider. Verify a paid test order reaches the correct supplier, check fulfillment and tracking, and make sure the customer-facing order information is accurate. A real supplier order may incur charges.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
The Dropshipping page says the module is not enabled.
This is an activation requirement, not a missing browser setting. Contact the team with your store address and chosen provider. Do not change server configuration yourself.
I added a supplier but orders are not being sent.
Check activation, authorized provider access, product mappings, supplier status, and payment status. Adding a supplier record does not complete every integration step.
Set prices for supplier products
Review supplier costs and use pricing rules deliberately before publishing products.
Illustrated guide: lulu.us.com/help/dropshipping-pricing
Before you startHave product, production, shipping, provider, and payment costs ready. Confirm the currency used by your store and supplier.
1. Review your full cost
Calculate the costs you expect to pay for a typical order. Include supplier costs and fulfillment, then account for shipping, fees, and any applicable charges for the markets you serve.
2. Open the pricing rules area
After dropshipping is activated, open its Pricing rules area. Check whether a store default or supplier-specific rule already exists before adding another.
3. Set a rule deliberately
Use Add pricing rule and the fields offered by your store. Confirm whether the rule applies to one supplier or the store default. The admin notes that without a rule, imported products can keep the supplier’s cost as their price.
4. Review minimum advertised prices
If your supplier requires a minimum advertised price, review the MAP setting and agreement before using discounts or publishing a lower price.
5. Check actual product prices
Inspect several imported or mapped products in Products, including variants with different costs. Confirm the displayed retail price and test the checkout total before promoting the range.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
A product imported at its supplier cost.
Review the store-default and supplier-specific pricing rule, then check the resulting retail price before publishing. Do not assume a missing rule adds a margin.
My selling price changed.
Review supplier cost updates, currency, and active pricing rules. Check whether an integration or repricing process updated the value.
Troubleshoot a dropshipping order
Find where an order stopped before you retry or contact the supplier.
Illustrated guide: lulu.us.com/help/dropshipping-order-troubleshooting
Before you startHave the Lulu order number and supplier reference ready. Do not place a duplicate order while the original result is uncertain.
1. Confirm the customer order
Open Orders and inspect the order’s payment and fulfillment states. An unpaid or pending order should not be treated as ready for supplier fulfillment.
2. Check the supplier record
Confirm the intended supplier is Active. A Paused supplier stops routing new orders; do not reactivate one until its service or account issue is resolved.
3. Check item mapping and availability
Compare the ordered variant with the supplier’s product identifier, SKU, options, and availability. A similar title is not enough to identify the correct item.
4. Review the fulfillment handoff
Open the dropshipping fulfillment-order view when available. Note the status, supplier reference, and error message. If the provider accepted the order but Lulu did not receive confirmation, ask the team to reconcile it before retrying.
5. Track the shipment and support the customer
Use available tracking and the provider’s order record to confirm shipment progress. Update the customer with verified information; do not promise a delivery date based only on a generic supplier estimate.
6. Escalate with useful evidence
Send the store address, order number, provider, reference, and exact error to support. Hide private addresses and credentials in screenshots. Coordinate returns under the provider’s process rather than assuming a refund cancels a shipment.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
There is no tracking yet.
Check whether the supplier has shipped the order. Tracking may arrive after dispatch or through the next supported update; an accepted order is not necessarily shipped.
The customer requested a refund after dispatch.
Review the order, shipment, and provider’s return process together. A payment refund and a parcel return are separate actions; confirm both responsibilities before proceeding.
Connect CJdropshipping to your store
Prepare your CJdropshipping account, map products, and verify fulfillment with the Lulu team.
Illustrated guide: lulu.us.com/help/connect-cj-dropshipping
Before you startA CJ account with the required API access and a chosen product range. Lulu dropshipping must be activated and configured before live orders.
1. Confirm activation first
Open Dropshipping in your admin. If it shows the activation message pictured here, contact the team with your store address and the provider you want to use.
2. Prepare your provider catalog
Choose products and review available delivery routes in your CJ account. Confirm the product options, stock, shipping cost, and estimated handling time before preparing listings.
3. Authorize the correct connection
Arrange the CJ authorization and product mapping with the Lulu team. Check that the account used for fulfillment has the required payment arrangements.
4. Review the storefront listings
Check each mapped product in Products. Confirm the title, images, variants, price, and availability. Keep unfinished listings in Draft until the details and fulfillment route are confirmed.
5. Set delivery and support expectations
Publish delivery and return information that reflects this provider’s actual terms for your products and markets. Product, production, fulfillment, and shipping charges are separate from Lulu.
6. Verify with a test order
Use an agreed test procedure to check payment, provider acceptance, fulfillment, and tracking. Review the resulting Lulu order and provider record together before opening the range to customers.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
Can I just enter my provider username and start selling?
No. Confirm provider approval or API permissions, account authorization, store activation, and variant mapping with the team. A provider account alone does not complete the connection.
The provider account is connected but an item fails.
Check the exact product and variant identifiers, account/shop selection, stock or production availability, destination, and provider billing status. Share the error and references with support before retrying.
Connect AliExpress to your store
Prepare your AliExpress account, map products, and verify fulfillment with the Lulu team.
Illustrated guide: lulu.us.com/help/connect-aliexpress-dropshipping
Before you startApproved AliExpress Dropshipping API access and an authorized account. Lulu dropshipping must be activated and configured before live orders.
1. Confirm activation first
Open Dropshipping in your admin. If it shows the activation message pictured here, contact the team with your store address and the provider you want to use.
2. Prepare your provider catalog
Review the specific seller, product, variant, shipping destination, and return terms. Different sellers can have different delivery and service conditions.
3. Authorize the correct connection
Arrange authorized AliExpress access with the team. Confirm the approved account and product identifiers; a regular buyer login alone does not establish an API connection.
4. Review the storefront listings
Check each mapped product in Products. Confirm the title, images, variants, price, and availability. Keep unfinished listings in Draft until the details and fulfillment route are confirmed.
5. Set delivery and support expectations
Publish delivery and return information that reflects this provider’s actual terms for your products and markets. Product, production, fulfillment, and shipping charges are separate from Lulu.
6. Verify with a test order
Use an agreed test procedure to check payment, provider acceptance, fulfillment, and tracking. Review the resulting Lulu order and provider record together before opening the range to customers.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
Can I just enter my provider username and start selling?
No. Confirm provider approval or API permissions, account authorization, store activation, and variant mapping with the team. A provider account alone does not complete the connection.
The provider account is connected but an item fails.
Check the exact product and variant identifiers, account/shop selection, stock or production availability, destination, and provider billing status. Share the error and references with support before retrying.
Connect Printful to your store
Prepare your Printful account, map products, and verify fulfillment with the Lulu team.
Illustrated guide: lulu.us.com/help/connect-printful-dropshipping
Before you startA Printful account with prepared designs and products. Lulu dropshipping must be activated and configured before live orders.
1. Confirm activation first
Open Dropshipping in your admin. If it shows the activation message pictured here, contact the team with your store address and the provider you want to use.
2. Prepare your provider catalog
Prepare your products and design files in Printful. Review variant options and order samples where appropriate before offering the range in your storefront.
3. Authorize the correct connection
Arrange Printful authorization and map the intended product variants. Confirm billing and production readiness before sending orders.
4. Review the storefront listings
Check each mapped product in Products. Confirm the title, images, variants, price, and availability. Keep unfinished listings in Draft until the details and fulfillment route are confirmed.
5. Set delivery and support expectations
Publish delivery and return information that reflects this provider’s actual terms for your products and markets. Product, production, fulfillment, and shipping charges are separate from Lulu.
6. Verify with a test order
Use an agreed test procedure to check payment, provider acceptance, fulfillment, and tracking. Review the resulting Lulu order and provider record together before opening the range to customers.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
Can I just enter my provider username and start selling?
No. Confirm provider approval or API permissions, account authorization, store activation, and variant mapping with the team. A provider account alone does not complete the connection.
The provider account is connected but an item fails.
Check the exact product and variant identifiers, account/shop selection, stock or production availability, destination, and provider billing status. Share the error and references with support before retrying.
Connect Printify to your store
Prepare your Printify account, map products, and verify fulfillment with the Lulu team.
Illustrated guide: lulu.us.com/help/connect-printify-dropshipping
Before you startA Printify shop, prepared products, and authorized account access. Lulu dropshipping must be activated and configured before live orders.
1. Confirm activation first
Open Dropshipping in your admin. If it shows the activation message pictured here, contact the team with your store address and the provider you want to use.
2. Prepare your provider catalog
Choose products and a print provider in Printify. Review available sizes, colors, production time, and shipping for your intended destinations.
3. Authorize the correct connection
Arrange the Printify connection for the correct shop. Confirm product mapping and whether the order has been sent into production before treating it as in fulfillment.
4. Review the storefront listings
Check each mapped product in Products. Confirm the title, images, variants, price, and availability. Keep unfinished listings in Draft until the details and fulfillment route are confirmed.
5. Set delivery and support expectations
Publish delivery and return information that reflects this provider’s actual terms for your products and markets. Product, production, fulfillment, and shipping charges are separate from Lulu.
6. Verify with a test order
Use an agreed test procedure to check payment, provider acceptance, fulfillment, and tracking. Review the resulting Lulu order and provider record together before opening the range to customers.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
Can I just enter my provider username and start selling?
No. Confirm provider approval or API permissions, account authorization, store activation, and variant mapping with the team. A provider account alone does not complete the connection.
The provider account is connected but an item fails.
Check the exact product and variant identifiers, account/shop selection, stock or production availability, destination, and provider billing status. Share the error and references with support before retrying.
Connect Amazon MCF to your store
Prepare your Amazon MCF account, map products, and verify fulfillment with the Lulu team.
Illustrated guide: lulu.us.com/help/connect-amazon-mcf-dropshipping
Before you startEligible stock already stored with Amazon and authorized selling-partner access. Lulu dropshipping must be activated and configured before live orders.
1. Confirm activation first
Open Dropshipping in your admin. If it shows the activation message pictured here, contact the team with your store address and the provider you want to use.
2. Prepare your provider catalog
Confirm the seller account, region, marketplace, SKUs, and available fulfillment inventory. Amazon MCF is a fulfillment service for your stock, not an inventory-free supplier catalog.
3. Authorize the correct connection
Arrange the authorized Amazon connection and SKU mapping. Check destination coverage, shipping options, and fulfillment charges for your intended orders.
4. Review the storefront listings
Check each mapped product in Products. Confirm the title, images, variants, price, and availability. Keep unfinished listings in Draft until the details and fulfillment route are confirmed.
5. Set delivery and support expectations
Publish delivery and return information that reflects this provider’s actual terms for your products and markets. Product, production, fulfillment, and shipping charges are separate from Lulu.
6. Verify with a test order
Use an agreed test procedure to check payment, provider acceptance, fulfillment, and tracking. Review the resulting Lulu order and provider record together before opening the range to customers.
Completion checklist
- Confirm activation, provider permissions, and product mapping.
- Review supplier costs, retail prices, and delivery expectations.
- Complete a test order before promoting supplier-fulfilled products.
Troubleshooting
Can I just enter my provider username and start selling?
No. Confirm provider approval or API permissions, account authorization, store activation, and variant mapping with the team. A provider account alone does not complete the connection.
The provider account is connected but an item fails.
Check the exact product and variant identifiers, account/shop selection, stock or production availability, destination, and provider billing status. Share the error and references with support before retrying.
Account access: sign in and reset your password
Find your store, complete email verification, and recover access.
Illustrated guide: lulu.us.com/help/sign-in-and-recover-access
Before you startUse the email address registered with Lulu. You need access to that inbox.
1. Sign in to Lulu
Use Log in on the Lulu website. Enter your account email and password, then choose the store you want to manage.
- Check the store name before making changes.
- An invitation to another store does not transfer ownership of your existing store.
2. Complete verification
If a verification code is requested, open the email sent to your account and enter the latest code.
- Use the resend option only after checking spam and waiting for delivery.
- Keep the sign-in window open while checking email.
3. Reset a forgotten password
Choose the forgotten-password option on the login screen. Request a reset email and follow its link to choose a new password.
- Use the newest reset link if you requested more than one.
- Return to login after the password-updated confirmation.
4. Review your account
Open Account to review your name, email, password, and logged-in devices. Revoke access from devices you no longer use.
- If you cannot access your email, contact support with your store address; do not send your password.
Completion checklist
- You can sign in and select the right store.
- Your recovery email is accessible.
Troubleshooting
Why does my reset link no longer work?
It may have expired or been replaced. Request a fresh reset email and use its link once. If delivery fails, check the exact account email with support.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
CSV: import and export products
Move a catalog using a spreadsheet and review the import before applying it.
Illustrated guide: lulu.us.com/help/import-export-products
Before you startExport the current catalog first. Keep an untouched copy for reference.
1. Export a template
Open Products → Export. Choose the CSV format for your spreadsheet program and download the catalog.
- Keep the column headings unchanged.
- A product with variants can occupy more than one row.
2. Prepare a small import
Edit a copy of the exported CSV. The importer matches rows by Handle, so preserve handles when updating existing products.
- Keep SKUs and barcodes as text so leading zeros survive.
- Review variant rows, prices, image URLs, and inventory columns.
- Try a few products before a large import.
3. Review the preview
Choose Products → Import and upload your CSV. Review the preview and any validation messages before choosing Import products.
- Resolve errors in the file and upload it again.
- Do not assume a spreadsheet file is CSV merely because you renamed it.
4. Inspect the result
Open imported products and verify variants, images, prices, and visibility. Export again if you need to compare the result with your source.
- Preview at least one imported product on the storefront.
Completion checklist
- The import result has no unresolved errors.
- Sample products match the source file.
Troubleshooting
Why did an import update an existing product?
Rows are matched using Handle. Review the import preview and use a distinct handle for a genuinely new product. Restore individual values from your saved export if necessary.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Variants: sizes, colors, SKUs, and prices
Manage the choices customers select within a product.
Illustrated guide: lulu.us.com/help/manage-product-variants
Before you startPrepare a unique SKU for each stock item and decide which options customers need.
1. Open the product
Go to Products and open a product, or choose Add product for a new one. Find its options and variants controls.
- Use short option names such as Size or Color.
2. Define the choices
Enter the option values that describe your actual stock. Review the generated variant combinations before saving.
- Remove combinations you do not sell.
- Keep names consistent across related products.
3. Review each variant
Set each variant’s price, SKU, inventory tracking, and available stock as appropriate.
- A product-level price does not replace a review of every variant.
- Confirm the location used for stock.
4. Test selection
Save, preview the product, and select each option on desktop and mobile. Add a sample variant to the cart.
- Check that the cart shows the chosen variant and correct price.
Completion checklist
- Every sellable combination has the right SKU and price.
- The storefront selector matches your stock.
Troubleshooting
Why is one size unavailable?
Check that the variant exists, is available for sale, and has sellable inventory at an eligible location. Also review any continue-selling setting.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Purchase orders: order and receive supplier stock
Track incoming stock, supplier costs, and partial receipts.
Illustrated guide: lulu.us.com/help/create-purchase-orders
Before you startCreate the products and receiving location before recording a purchase order.
1. Start a purchase order
Open Products → Purchase orders → Create purchase order. Enter the supplier and the receiving details shown in the editor.
- Use a supplier reference you can match to the supplier invoice.
2. Add products and costs
Choose Add product. Enter quantities and unit costs, then review tax, shipping, and any landed costs.
- Check the currency and totals.
- Save the draft before placing the supplier order.
3. Record the order
After placing the order with your supplier, choose Mark as ordered.
- Recording a purchase order does not by itself prove that the supplier received an order or payment.
4. Receive actual quantities
When goods arrive, choose Receive items and enter the quantities physically received.
- Record partial deliveries separately.
- Check Inventory after receiving; do not count incoming goods as available before receipt.
Completion checklist
- The purchase order matches the supplier reference.
- Received quantities agree with physical stock.
Troubleshooting
Why is the order only partially received?
Some ordered units have not been received. Compare delivery paperwork with the remaining quantities and record the next receipt when it arrives.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Transfers: move stock between locations
Record stock moving from one location to another.
Illustrated guide: lulu.us.com/help/transfer-inventory
Before you startBoth locations and the product variants must already exist.
1. Create a transfer
Open Products → Transfers → Create transfer. Select the source and destination locations.
- Choose different locations and verify available stock at the source.
2. Add the shipment
Add products, enter quantities, and add a reference or note that identifies the movement. Save the transfer.
- Count the physical units before dispatch.
3. Mark the movement
Choose Mark as in transit when the goods leave the source.
- Do not also make a manual inventory increase for the same movement.
4. Receive and reconcile
At the destination choose Receive items and record the actual quantities received. Check both locations in Inventory.
- Investigate missing or damaged units before closing your operational records.
Completion checklist
- Source and destination quantities reflect the movement.
- The transfer status agrees with the physical shipment.
Troubleshooting
Why is stock still in transit?
The destination receipt has not been completed, or only part was received. Open the transfer and check its remaining quantities.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Landed costs: understand your product margin
Account for additional costs when reviewing supplier and group margins.
Illustrated guide: lulu.us.com/help/calculate-landed-costs
Before you startHave supplier unit costs and your own shipping, duty, and handling figures ready.
1. Create a cost profile
Open Products → Landed costs and choose Add profile. Name it for the cost scenario it represents.
- Use a name your team can distinguish from other profiles.
2. Add cost components
Enter the components offered by the editor and review their calculation order.
- Keep percentage and fixed components distinct.
- Use your actual cost assumptions, not the customer shipping charge.
3. Record purchase costs
For a specific shipment, open its purchase order and review the Landed costs section. Add the applicable costs.
- Check the allocation and total before saving.
4. Review the result
Use the landed-cost analytics and group margin views where available. Investigate products without a unit cost before relying on margin totals.
- Revisit assumptions when supplier or freight prices change.
Completion checklist
- The cost profile has the intended components.
- Margin calculations include recorded unit costs.
Troubleshooting
Why are some variants excluded from margin?
Their unit cost may be missing. Add the cost and check the report again; sales price alone cannot establish margin.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Draft orders: create an order and send an invoice
Prepare a manual order before taking payment.
Illustrated guide: lulu.us.com/help/draft-orders-and-invoices
Before you startConfirm the customer, items, and agreed prices. Sending an invoice contacts the customer.
1. Create the draft
Open Orders → Drafts → Create order. Select the customer or create the record needed for this sale.
- Check the customer email before sending anything.
2. Build the order
Choose Add product, or Add custom item for a line outside the catalog. Set quantities and review the payment total.
- Review market, notes, and tags.
- Check shipping, discounts, and taxes shown by the editor.
3. Save or invoice
Choose Save as draft to return later. Choose Send invoice only when the draft is ready for the customer.
- Review the recipient and invoice details before confirming.
4. Record payment correctly
Use Mark as paid only after you have actually received the payment. Follow the resulting order in Orders for fulfillment.
- Marking an order as paid is not a bank transfer or card charge.
Completion checklist
- The draft contains the agreed items and customer.
- Payment status reflects actual money received.
Troubleshooting
Why is an invoice-sent draft not a paid order?
Sending an invoice requests payment. Check the payment outcome before marking the order paid or fulfilling it.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Refunds and cancellations: correct an order
Review refundable quantities, restocking, and cancellation status.
Illustrated guide: lulu.us.com/help/refund-and-cancel-orders
Before you startYou need permission to change orders. Check the payment and fulfillment state first.
1. Find the original order
Open Orders, search for the order, and inspect its items, payment history, and fulfillment.
- Confirm the customer and order number.
- Check whether an earlier refund already exists.
2. Prepare a refund
Choose Refund when available. Enter item quantities, a reason, and the refund amount.
- The amount must fit the remaining refundable balance.
- Select Restock items only for stock that should become sellable again.
3. Confirm and reconcile
Review the amount and submit once. Check the order timeline and the payment provider outcome before promising a completed bank refund.
- Manual payment methods may require a separate return of funds.
- If an error occurs, check existing records before retrying.
4. Cancel when appropriate
Use the order’s Cancel order action for an order that should not proceed. Review the cancellation options and confirm.
- Contact fulfillment or the supplier separately if dispatch has already started.
- Cancellation does not retrieve a shipped parcel.
Completion checklist
- The order history shows the intended change.
- Stock and the payment-provider record have been reconciled.
Troubleshooting
Why is Refund unavailable?
Check your permissions, the payment state, and the remaining refundable balance. Ask support if the order and provider records disagree.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Abandoned checkouts: review incomplete purchases
Find incomplete checkouts and review recovery settings.
Illustrated guide: lulu.us.com/help/abandoned-checkouts
Before you startA checkout is not a paid order. Use customer contact details only for the purpose allowed by their consent and your policy.
1. Open incomplete checkouts
Go to Orders → Abandoned checkouts. Review the records available for your store.
- Check the date and customer details before investigating.
2. Look for friction
Compare the affected products and customer destination with your stock, payment, and shipping setup.
- Reproduce the journey with your own test details.
- Check for a destination with no shipping rate.
3. Review recovery settings
Open Settings → Checkout and find Abandoned checkout emails. Review the available controls and save intended changes.
- Use a test inbox to verify the recovery journey before relying on it.
4. Measure recovery
Compare recovered purchases with actual Orders. Avoid treating a reminder being sent as a completed sale.
- Check whether the customer already completed a later order.
Completion checklist
- Checkout obstacles have been checked.
- Recovery is measured using actual completed orders.
Troubleshooting
Why is the list empty?
There may be no recorded abandoned checkouts for this store. A visitor who only browses or adds to cart may not create a checkout record.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Gift cards: issue, manage, and report
Create a gift card and track its balance and status.
Illustrated guide: lulu.us.com/help/issue-gift-cards
Before you startIssuing a gift card creates spendable value. Verify the amount and recipient before creating it.
1. Create a gift card
Open Products → Gift cards → Create gift card. Enter the Initial value in the store currency.
- Review the optional expiration date shown in the form.
2. Identify the recipient
Select a customer if appropriate and add an internal note explaining why the card is being issued.
- Internal notes are for staff.
- Check that the recipient is the intended customer.
3. Save the code securely
Create the gift card and copy the code from the confirmation screen. Deliver it privately to the recipient.
- Do not include live gift card codes in screenshots or public support messages.
4. Monitor use
Return to Gift cards to search by the last four digits or customer email. Open Reports to review issuance and redemptions.
- Check the remaining balance and status before replacing a card.
Completion checklist
- The initial value and recipient are correct.
- The code has been delivered privately.
Troubleshooting
Why does a customer’s gift card fail?
Check its status, expiration if configured, and remaining balance. Verify the code privately without posting it publicly.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Segments: group customers by conditions
Build a reusable customer group and inspect who matches.
Illustrated guide: lulu.us.com/help/create-customer-segments
Before you startHave customer records in your store and a clear purpose for the group.
1. Start from a segment
Open Customers → Segments. Inspect an existing segment or choose Create segment.
- Existing examples include purchased customers and email subscribers.
2. Set the query
Use the segment editor’s Query controls to define the conditions.
- Use the syntax and suggestions offered in the editor.
- Give the segment a descriptive name.
3. Inspect matching customers
Review the Customers result before saving. Adjust conditions if the list is too broad or empty.
- A segment based on purchases does not automatically mean email-marketing consent.
4. Save and revisit
Save the segment and reopen it to confirm the stored query. Recheck membership when using it in a campaign.
- Keep campaign consent checks separate from audience selection.
Completion checklist
- The query matches the intended customers.
- The segment can be reopened from the list.
Troubleshooting
Why are no customers included?
Review each condition and whether any stored customer data matches it. Start with a broader condition and narrow it gradually.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Pages: publish About, Contact, and information pages
Create useful storefront pages and make them easy to find.
Illustrated guide: lulu.us.com/help/publish-store-pages
Before you startPrepare the copy and choose where the page should appear in navigation.
1. Add a page
Open Online Store → Pages → Add page. Enter a clear title such as About us or Delivery information.
- Start with one customer question per page.
2. Write and review
Enter the page content and review its handle and visibility controls.
- Use short paragraphs and descriptive links.
- If entering HTML, use trusted content and check the rendered result.
3. Save and view
Save the page and use its View on store link. Read the page on desktop and a phone.
- Check links, headings, images, and contact details.
4. Add navigation
Open Content → Menus and link the page from the appropriate header or footer menu.
- Saving a page alone does not make it easy for customers to discover.
Completion checklist
- The page opens at the intended URL.
- A menu links to the page.
Troubleshooting
Why can’t visitors find my page?
Check visibility and add a menu link. If the entire storefront is password protected, visitors also need store access.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Blog: write and publish posts
Publish useful articles with an author, summary, and image.
Illustrated guide: lulu.us.com/help/publish-blog-posts
Before you startPrepare original copy and an image you have permission to use.
1. Create a post
Open Content → Blog posts → Create blog post. Enter the title and author.
- Use a title that describes the subject clearly.
2. Add the story
Enter the excerpt and article body. Add an appropriate image using the available field.
- Make the excerpt useful without repeating the whole article.
- Check image quality and mobile readability.
3. Review visibility
Set the visibility and publication details available in the editor, then save.
- Keep unfinished posts hidden until reviewed.
4. Open the published article
Check the storefront article and its links. Add a route to the blog through store navigation where appropriate.
- Review older articles when product details change.
Completion checklist
- The post has the correct visibility.
- The storefront article reads well on a phone.
Troubleshooting
Why is the post not visible?
Reopen it and check visibility and publication details. Also confirm your theme and navigation expose the blog.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Files: upload images, videos, and PDFs
Host reusable media in your store and use it in content.
Illustrated guide: lulu.us.com/help/upload-store-files
Before you startPrepare optimized files you own or are licensed to publish.
1. Open the file library
Go to Content → Files → Upload files. Choose a supported image, video, or PDF.
- Videos use supported MP4 or WebM formats.
- Follow the type and size limits displayed by the uploader.
- How much you can store depends on your plan. Basic: 100 GB of files, 50 GB of video, 250 videos and 3D models. Grow: 300 GB, 500 GB and 1,000. Advanced: 500 GB, 500 GB and 5,000. Plus: 1 TB, 2 TB and 50,000. The top of Content → Files shows how much you have used.
2. Check the upload
Wait for the upload to finish, then locate the file in the library.
- Use meaningful filenames so your team can find assets later.
3. Use the hosted file
Use its hosted address or the media picker provided by the page or theme editor.
- Use store-hosted media instead of hotlinking another website.
- Provide descriptive alternative text wherever the editor supports it.
4. Verify before removing
Preview the content that uses the file. Before deleting a file, check whether pages, products, or theme sections still reference it.
- Deleting a shared file can break more than one page.
Completion checklist
- The uploaded file opens successfully.
- The page using it loads correctly on mobile.
Troubleshooting
Why was a file rejected?
Check its true file type and size against the uploader’s message. Export to a supported format or reduce its size, then upload again.
An upload says I have run out of storage.
Check the usage at the top of Content → Files. Delete files you no longer need, or move to a plan with more storage.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Store access: password protection and preview links
Keep a store private during setup and open it when ready.
Illustrated guide: lulu.us.com/help/manage-store-access
Before you startComplete your launch checklist before opening your store. The first launch goes through the Go live page.
1. Find access settings
Open Online Store → Preferences → Password protection. Review whether Enable password is on.
- The storefront password is separate from your admin account password.
2. Set the visitor experience
For a private store, set the storefront password and message to visitors, then Save.
- Share access only with reviewers who need it.
3. Use preview links carefully
In Store links, copy the store URL or private preview link as appropriate. A preview link can bypass password protection.
- Do not publish a private preview link in public documentation.
4. Open the store
The first time, open the Go live page (Home > Go live, or Online Store > Preferences > Go live): its checklist confirms your package, paid apps and theme are settled, then switches the store to production. After launch, Online Store > Preferences > Store status switches between Development and Production. Visit the public URL in a private browser window without an admin session.
- Review search indexing separately under SEO & AI.
Completion checklist
- A logged-out visitor gets the intended access.
- Private preview links remain private.
Troubleshooting
Why can I see the store while visitors cannot?
Your browser may have a valid preview link or storefront access. Test the ordinary store URL in a new private window.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
SEO: search visibility, metadata, and redirects
Control discovery settings and fix common search presentation issues.
Illustrated guide: lulu.us.com/help/configure-search-visibility
Before you startHave a public-ready storefront. Search engines decide when and how to index pages.
1. Review indexing
Open Online Store → SEO & AI. Review Search engine indexing and save the intended setting.
- A private or unfinished store should not be treated as ready for public discovery.
2. Set search appearance
Review the home page title, meta description, and social-sharing image in SEO & AI or Preferences.
- Describe your business accurately.
- Use a local uploaded sharing image and check the preview.
3. Review crawler choices
In SEO & AI, review AI crawler and answer-engine controls separately from search-engine indexing.
- Choose the access policy you actually want; enabling a crawler does not guarantee a mention.
4. Repair old paths
Use Online Store → Preferences → URL redirects for changed addresses. Enter the old path and intended destination.
- Open the old URL to test the result.
- Use SEO health to review remaining product issues.
Completion checklist
- Indexing and crawler choices are intentional.
- Titles, descriptions, and redirects have been checked.
Troubleshooting
Why is my store not appearing in search yet?
Check password protection and indexing first. Search-engine discovery is not immediate or guaranteed; changes in Lulu do not force a search-engine update.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Custom content: metafields and metaobjects
Store structured details beyond the standard product fields.
Illustrated guide: lulu.us.com/help/metafields-and-metaobjects
Before you startDecide whether you need one extra field or a reusable structured content type.
1. Choose a data structure
Use Metafields for an extra value attached to a resource. Use Content → Metaobjects for a reusable definition with entries.
- Examples include a material field or a reusable size-guide entry.
2. Create a definition
In Metafields choose Add definition, or create a definition under Metaobjects. Set the name, key or namespace, and field type offered by the editor.
- Choose stable keys; existing theme connections may depend on them.
3. Enter values
Populate the field on the relevant resource or create metaobject entries.
- Keep values consistent with the selected type.
- Set storefront visibility only for content intended to be public.
4. Connect and preview
Use a compatible theme section or customization to display the content. Preview a resource with a value and one without.
- Saving structured data alone does not automatically add a visible theme section.
Completion checklist
- The definition and sample values are saved.
- The theme displays the intended public content.
Troubleshooting
Why is my custom field not on the product page?
The theme needs a compatible connection to that field and the field must permit storefront access. Ask support to connect it if the editor does not offer that option.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
General settings: business details, contact details and defaults
Record the business behind your store, the contact details and address customers see, and the defaults your store runs on.
Illustrated guide: lulu.us.com/help/configure-general-settings
Before you startUse the store owner account, or an account with the Manage settings permission. Have your legal business name, address and (for an individual) your date of birth ready.
1. Open General
Go to Settings → General. The page has four cards, in this order: Business details, Store contact details, Store defaults and Order processing.
2. Add or edit your business details
In Business details, click Add business details — or, once they are saved, click the … menu next to your business and choose Edit. A full-screen editor opens.
- Under "What type of business do you have?", choose your country/region and the business type: Individual, Sole proprietorship, Partnership, Private company / Corporation, Public company, Non-profit or Other.
- Individual or sole proprietor: enter your first and last name, date of birth (optional, you must be at least 18), email, phone number and residential address. A sole proprietor can also add a business name and tax ID.
- Company, partnership or non-profit: enter the legal business name, registration number and tax ID / VAT number (both optional), the business address, phone and email, and the authorised representative’s name and job title.
- Open "Add personal information" to store an optional personal ID number. It is stored encrypted and never shown in full again: at most the last 4 characters of a long ID, or the last 2 of a short one. Click Remove to delete it.
- Switching from Individual or Sole proprietorship to a company type removes the date of birth and personal ID when you save. The editor warns you before you do.
- Click Save. If a field needs fixing, it is highlighted with a message under it.
3. Edit your store’s contact details
In Store contact details, click the first row (your store name, email and phone) to edit the store name, store phone and store contact email. Click Store address to edit the address.
- The store address has a legal business name, country/region, address, apartment or suite, city, state/province and postal code. For the United States, Canada and Australia, pick the state or province from the list.
- Your store address appears on invoices, policy templates and the footer of marketing emails.
- If you entered an address before these fields existed, it is shown as it was and pre-filled into Address. Split it into the fields, then save.
4. Review store defaults
In Store defaults, check the store currency, unit system, default weight unit, time zone, backup region, order ID prefix and suffix, cart wording and what happens after a customer adds to cart. Click Save in that card.
- Changing the store currency asks whether to convert your prices or only change the symbol. Read the summary before you confirm.
- Backup region is the country/region whose settings apply to customers outside all of your markets. A customer from a country that none of your markets includes gets the currency, prices, taxes and return rules of the market that includes your backup region. The list shows the countries in your active markets. If you pick a country that isn't in any market, or you later remove it from its market, the backup region isn't used. It also isn't used when one of your markets already serves the rest of the world.
5. Review order processing
Choose whether paid orders are fulfilled automatically and whether finished orders are archived, then click Save in that card.
- Do not turn on an automatic action without knowing when it runs.
Completion checklist
- Your business details name the right person or company and country.
- The store name, contact email, phone and address are what customers should see.
- Store defaults match how you sell, including the time zone and currency.
Troubleshooting
Why can't I see my business details?
Business details contain personal information, so only the store owner and users with the Manage settings permission can view or edit them. That includes collaborator (partner) accounts that were given Manage settings, so give that permission only to people you trust with these details. Ask the owner if you need access.
My personal ID shows only dots and a few characters. Did it save?
Yes. The full number is stored encrypted and never shown again. Leave the field as it is to keep it, type a new number to replace it, or click Remove to delete it. If it says "Saved ID can't be displayed", the saved ID is still kept; enter it again to replace it.
It says I must be at least 18 years old.
The date of birth on an individual or sole proprietor must be for someone aged 18 or over. Check the year, or leave the date of birth empty.
Why do I still see my old address on an invoice or email?
Invoices and emails already sent keep the address they were created with. New ones use the address you saved. Theme text and notification templates you typed by hand need to be changed separately.
Checkout: contact details, accounts, and options
Choose the information collected during checkout.
Illustrated guide: lulu.us.com/help/configure-checkout
Before you startKnow which information is necessary to deliver your products.
1. Open Checkout
Go to Settings → Checkout. Review Configuration and Customer contact method.
- Choose the contact information your fulfillment process needs.
2. Review customer fields
Set the available Customer information and Customer accounts options.
- Avoid requiring information that your process does not need.
3. Review order options
Inspect Marketing options, Terms of service, Tipping, and other order controls shown in this store.
- Marketing consent should be a deliberate customer choice.
- Keep customer-facing wording consistent with your policies.
4. Test the form
Save and run through checkout on desktop and mobile with your own test details.
- Check required-field messages and the final total.
- Verify payment and shipping choices for a supported destination.
Completion checklist
- Required fields fit your delivery process.
- A mobile customer can complete the test journey.
Troubleshooting
Why does checkout ask for unexpected information?
Review the saved checkout options and the product’s delivery requirements. Use a fresh checkout session when testing changes.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Locations: set up where stock is held
Keep inventory tied to the places that store and fulfill it.
Illustrated guide: lulu.us.com/help/configure-locations
Before you startKnow each location’s address and whether it fulfills online orders.
1. Review locations
Open Settings → Locations and inspect your existing locations.
- Do not create a duplicate because a location’s display name changed.
2. Add or edit a location
Use the location controls to enter its name and address. Review the fulfillment options offered on the screen.
- Use names your warehouse team can distinguish.
3. Assign inventory
Open Inventory and select the location. Verify which variants are stocked there and their quantities.
- Use a transfer when moving existing physical stock between locations.
4. Check delivery
Review shipping origins and rates, then test an order for stock at this location.
- Resolve stock and shipping eligibility before sending customer traffic.
Completion checklist
- Location addresses and stock are accurate.
- The intended fulfillment location can serve a test order.
Troubleshooting
Why can’t I sell stock at a location?
Check the variant’s available inventory and the location’s fulfillment eligibility. Stock existing somewhere does not guarantee that checkout can ship it.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Taxes and duties: enter your store configuration
Find the tax controls and validate their effect on a test checkout.
Illustrated guide: lulu.us.com/help/configure-taxes
Before you startHave the applicable registrations and settings confirmed by your accountant or adviser. This guide explains the interface, not which tax obligations apply.
1. Open tax settings
Go to Settings → Taxes and duties and review the controls available for the store.
- Keep a record of the configuration you intend to apply.
2. Enter the confirmed setup
Apply the rates, regions, or tax-included choices supported by your settings screen.
- Do not assume another store’s settings apply to your business.
3. Review taxable products
Check relevant product tax settings and your shipping treatment.
- Include a representative taxable product in your test.
4. Verify the calculation
Save and test checkout with representative destination addresses. Compare the breakdown with the expected result supplied by your adviser.
- Resolve a mismatch before taking live orders.
Completion checklist
- Saved settings match your confirmed requirements.
- Test totals show the expected tax treatment.
Troubleshooting
Why does tax differ by checkout address?
The destination, product treatment, and saved tax setup can affect the total. Compare those inputs and ask support to investigate a calculation mismatch.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Notifications: review customer emails
Review templates and confirm that customer messages contain the right information.
Illustrated guide: lulu.us.com/help/configure-notifications
Before you startUse a test inbox you control. Never put payment secrets in notification templates.
1. Find notifications
Open Settings → Notifications and choose the message type you want to review.
- Distinguish customer messages from internal staff notifications.
2. Edit supported content
Review the subject and content controls provided by the template editor.
- Preserve the template variables needed for order details.
- Use the variable list shown beside the template rather than inventing variable names.
3. Preview and save
Use the available preview or test controls, then save the template.
- Check business contact details, links, and spelling.
4. Test a real workflow
Trigger the corresponding action using a test order and inbox. Verify the received message and destination links.
- Check spam if the message does not arrive.
- An order-state change and email delivery are separate outcomes.
Completion checklist
- The template is saved with valid variables.
- A test recipient receives the expected message.
Troubleshooting
Why is an email missing?
Check the recipient address and spam folder, then verify the action that should trigger it. Share the order reference and time with support if delivery remains missing.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Policies and privacy: publish customer information
Add store policies and review customer privacy controls.
Illustrated guide: lulu.us.com/help/policies-and-customer-privacy
Before you startPrepare policies suited to your business and regions. Lulu settings do not replace professional review of legal requirements.
1. Add policy text
Open Settings → Policies. Review Refund policy, Privacy policy, Terms of service, Shipping policy, and Contact information.
- Replace example or incomplete text with your own reviewed policies.
2. Check practical details
Ensure the policies explain the actual delivery, contact, and return process you can provide.
- Keep supplier return rules consistent with customer promises.
3. Review privacy controls
Open Settings → Customer privacy and inspect the available settings. For regional differences, review the market’s Customer privacy page too.
- Use the choices appropriate to your confirmed obligations.
4. Check storefront links
Save and visit the storefront. Verify policy links from the footer and relevant checkout locations.
- Make sure the published text matches the latest saved version.
Completion checklist
- Customers can open the intended policies.
- Privacy choices have been reviewed for the store.
Troubleshooting
Why is my policy not in the footer?
Check the theme and footer navigation. Add a link in Content → Menus if the theme does not expose the policy automatically.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Brand and languages: maintain store identity
Review brand assets and the languages configured for your store.
Illustrated guide: lulu.us.com/help/brand-and-languages
Before you startPrepare your logo files and reviewed translations.
1. Review Brand
Open Settings → Brand and add or review the brand assets and fields available there.
- Use clear logo artwork that works on light and dark backgrounds.
2. Check the theme
Open your theme editor and confirm how the logo, colors, and other brand choices appear.
- Some theme sections have their own settings; a brand record does not replace a preview.
3. Review Languages
Open Settings → Languages and inspect the supported language controls.
- Only enable languages you can support with complete customer-facing content.
- Do not assume enabling a language automatically translates every page or app.
4. Test customer journeys
Preview the storefront, navigation, product pages, and checkout in the intended language.
- Check long labels on a narrow phone screen.
Completion checklist
- Brand assets are clear across screen sizes.
- Enabled languages have reviewed content.
Troubleshooting
Why is some text still in another language?
It may come from product content, a theme section, or an app. Review each source and ask support about fields without a translation control.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Backups: download and preview a restore
Create a backup and understand the restore preview before changing store data.
Illustrated guide: lulu.us.com/help/backup-and-restore
Before you startUse an authorized account. Restoring data can replace current values; take a fresh backup first.
1. Download a backup
Open Backup and restore from the admin or Settings. Review What a backup contains, then use the download action.
- Store the backup privately; it can contain business data.
2. Inspect the scope
Read the listed included and excluded sections. Keep separate copies of anything the backup does not include.
- Do not assume a backup includes provider credentials, external-service data, or every uploaded asset.
3. Preview a restore
Under Restore from a backup, select the intended backup and run the preview. Check the source store, date, currency, warnings, and section plan.
- The preview says that nothing has been written yet.
- Stop if the source or scope is wrong.
4. Confirm only after review
Use Restore now and the final confirmation only when you intend to apply the displayed changes. Review the report and verify affected data afterward.
- Test key storefront flows after a restore.
- Contact support before restoring an unfamiliar file.
Completion checklist
- A current backup is stored privately.
- Any restore plan has been reviewed before confirmation.
Troubleshooting
Does previewing a backup change my store?
The restore preview reports the plan without writing it. Applying the restore requires the restore action and confirmation; review those screens carefully.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Security: account details and logged-in devices
Change your password and remove access from old devices.
Illustrated guide: lulu.us.com/help/secure-account-and-devices
Before you startMake sure you can receive messages at your account email before changing it.
1. Open Account
Use the account menu to open Account. Review your name, phone, and email.
- These are account details, separate from public store contact details.
2. Change credentials
Use the Password controls to change your password. For an email change, follow the displayed verification-code process.
- Use a unique password.
- Review the available two-step verification controls on this screen.
3. Review devices
Open Logged-in devices and inspect the sessions listed for your account.
- Check device descriptions and last activity before revoking sessions.
4. Remove access
Sign out a specific old device or use the relevant unrecognized, inactive, or other-device action. Confirm the intended scope.
- If you suspect account access was compromised, also change the password and contact support.
Completion checklist
- Your email and password are current.
- Unwanted sessions have been revoked.
Troubleshooting
Will signing out other devices close this session?
Use the action specifically labeled for other devices and read its confirmation. Individual and bulk actions have different scopes.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Billing: invoices, app charges, and plan changes
Find your bills and distinguish store, app, and provider charges.
Illustrated guide: lulu.us.com/help/billing-app-charges-and-cancellation
Before you startUse an account with billing access. Read the live amount and currency before confirming any purchase.
1. Review the store plan
Open Settings → Plan and inspect your current package, store status, and available change controls.
- Use the live billing screen for the amount and effective terms.
2. Inspect bills
Open Settings → Billing. Review the current billing cycle, Past bills, and Download actions.
- Match the bill to the correct store and billing period.
3. Review recurring apps
Inspect App subscriptions and Charges. Open the installed app and its listing to check the plan, usage limit, and cancellation controls.
- An external provider can bill separately.
- Do not assume uninstalling an app cancels a separate provider contract.
4. Change or close carefully
Read the confirmation before a plan change or cancellation. Your package is changed or cancelled under Settings → Billing → Change package ("Upgrade", "Downgrade" or "Cancel package"); an app plan with "Cancel plan" on the app's listing. If an action you need is not shown, contact support with the store address and request.
- Export needed records before closing a store.
- Keep the confirmation of any cancellation.
Completion checklist
- Bills and recurring services have been identified.
- Changes have a clear confirmation and effective terms.
Troubleshooting
Why is a charge different from the website price?
Check currency, billing period, taxes, usage, and separate app charges in the actual bill. Ask support to reconcile an unexplained difference before repeating a payment.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Markets: regional settings, catalogs, and rollouts
Organize regional selling settings and review inherited defaults.
Illustrated guide: lulu.us.com/help/manage-markets
Before you startPrepare the regions, delivery coverage, and currencies your business supports.
1. Create or inspect a market
Open Markets. Review Store default, then open an existing market or choose Create market.
- Give the market a clear name and set its region conditions.
2. Review inheritance
Inspect Customized and Inherited settings. Change only the settings that should differ from the store default.
- Verify currency, language, shipping, and customer privacy where offered.
3. Review catalogs and changes
Use Catalogs to inspect attached pricing. Use Rollouts to review scheduled or grouped changes before applying them.
- Check the setting key and new value for each rollout change.
4. Test the region
Save and test the storefront and checkout using a representative destination in the market.
- An active market still needs valid shipping and payment coverage.
Completion checklist
- Regions and overrides are intentional.
- A customer in the target region can complete the intended checkout.
Troubleshooting
Why did a market change when I edited a default?
Inherited settings follow the store default. Inspect the market’s Customized and Inherited sections before overriding a value.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
B2B: companies and wholesale price lists
Manage company accounts, payment terms, and negotiated prices.
Illustrated guide: lulu.us.com/help/wholesale-companies-and-price-lists
Before you startConfirm the commercial terms and who can buy on behalf of each company.
1. Add a company
Open Customers → Companies → Add company. Enter its details and the payment terms offered by the form.
- Check the company identity and contacts before giving access.
2. Create pricing
Choose Create price list. Set the adjustment or fixed product prices provided by the editor.
- Check whether an adjustment is a percentage or fixed amount.
- Confirm the currency.
3. Connect the company
Open the company record and review its contacts, locations, and pricing assignments.
- Apply the intended price list to the correct company or location.
4. Verify the buyer experience
Test with an authorized company customer and inspect product prices and checkout terms.
- Compare a retail customer’s view so negotiated prices are not exposed accidentally.
Completion checklist
- Company contacts and terms are correct.
- An eligible buyer receives the intended pricing.
Troubleshooting
Why does a buyer see retail prices?
Check the buyer’s company association and the price-list assignment, then start a fresh customer session.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
POS: registers, devices, staff, and receipts
Prepare an in-person selling location and register.
Illustrated guide: lulu.us.com/help/set-up-point-of-sale
Before you startConfirm POS access, a stock location, and the staff who will use the register.
1. Complete the setup checklist
Open Point of Sale. Review the setup checklist and choose Registers → Add register.
- Name the register and bind it to the intended location.
2. Pair a device
Open Devices → Pair new device. Use the one-time pairing code on the intended browser or tablet.
- Keep pairing codes private.
- Revoke or re-pair a device when it changes hands.
3. Set staff and receipt options
Use Staff & PINs to set authorized staff PINs. Open Settings to review receipts, tipping, taxes, payment types, and offline limits.
- Each staff member should use their own access.
- Verify the receipt business details.
4. Test the register
Choose Open register and test the selling workflow with approved test arrangements. Review Sessions and Reports afterward.
- Check stock comes from the correct location.
- Recording a tender does not itself connect a card terminal.
Completion checklist
- The register, device, and staff are configured.
- A test receipt and stock change have been verified.
Troubleshooting
Why can’t a device open a register?
Check pairing status, the register’s availability, and the staff PIN. Review any existing open drawer session before opening another.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
POS: cash sessions, reports, and barcode labels
Reconcile register activity and print product labels.
Illustrated guide: lulu.us.com/help/pos-sessions-and-labels
Before you startSet up a register and staff access first.
1. Open a drawer session
Open the register and follow its session-opening prompts. Record the actual opening cash where requested.
- Use the assigned location and staff identity.
2. Track and close
Record cash movements through the register’s supported actions. At closing, count the actual cash and complete the session close process.
- Investigate differences instead of changing the count to match a report.
3. Review reports
Open Point of Sale → Sessions for the session record. Use Reports for tender, staff, register, hour, and cash drawer movements.
- Choose the correct date range.
4. Print labels
Open Print labels, add products, select quantities, and choose the template and fields. Print a small test sheet first.
- Verify the barcode scans to the correct variant.
- Check printer scaling before a larger run.
Completion checklist
- The cash session is reconciled.
- A sample label scans correctly.
Troubleshooting
Why do labels print at the wrong size?
Check the selected template, printer paper size, and browser print scaling. Test one label before printing the full batch.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Google and Facebook: connect product feeds
Find your catalog feed and configure the channel connection.
Illustrated guide: lulu.us.com/help/google-and-facebook-channels
Before you startHave the relevant merchant or business account. External approval and service requirements are separate from Lulu setup.
1. Choose the channel
Open Google & YouTube or Facebook & Instagram in the admin. Read How to connect on that screen.
- Use the account belonging to this business.
2. Turn on the feed
In Connection, turn on the channel’s feed and save. The feed URL answers only while the channel’s app is installed and its feed is on. Merchant, catalog and pixel identifiers are optional: the feed works without them, so enter them for your records once you have them.
- Copy identifiers from the provider’s own business tools.
3. Register the feed
Copy Your product feed URL or Your catalog feed URL and add it to the provider using the channel’s displayed instructions.
- Review Products in your feed before submitting it, including any warnings.
- Each variant is sent as its own feed item, so the provider’s item count is usually higher than your product count.
4. Check provider diagnostics
Review feed processing and approval in the provider account. Fix rejected products and allow the feed to refresh.
- A saved connection does not guarantee listing approval or paid advertising.
Completion checklist
- The provider has the correct feed URL.
- Feed diagnostics have been reviewed.
Troubleshooting
Why are products absent from the provider?
Check the Lulu feed contents, provider processing errors, product availability, and account approval status.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Marketplace channels: activation, listings, and sync
Connect available external marketplaces and monitor listing and order synchronization.
Illustrated guide: lulu.us.com/help/marketplace-sales-channels
Before you startA marketplace merchant account and Lulu channel activation may be required.
1. Check activation
Open Marketplaces under Sales channels and choose a platform. Read its connection status.
- If it says Not yet enabled by Lulu, contact support before planning a live launch.
2. Connect the account
Use the channel’s connection action and complete the provider authorization when available.
- Confirm the correct marketplace account and region.
3. Publish a small selection
Select a few eligible products and choose Publish / Update. Inspect the resulting listing status and external identifiers.
- Use Sync price & stock after checking the intended prices and inventory.
4. Monitor orders and messages
Use the channel’s supported order and message actions. Compare imported orders with the marketplace before fulfillment.
- Do not publish the whole catalog until a small end-to-end test succeeds.
Completion checklist
- The channel shows a confirmed connection.
- A sample listing and order flow have been checked.
Troubleshooting
Why is synchronization unavailable?
The channel may not be enabled, the account may be disconnected, or provider authorization may have expired. Resolve the displayed status before retrying.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Multi-vendor marketplace: sellers and policies
Review marketplace activation, seller onboarding, and commission settings.
Illustrated guide: lulu.us.com/help/run-a-multi-vendor-marketplace
Before you startConverting a store to a marketplace changes its operating model. Agree the seller process with your team first.
1. Review marketplace mode
Open Marketplace and inspect whether the store is a marketplace operator or seller. Read the activation prompt if it is neither.
- Ask support to confirm fit before converting an established retail store.
2. Set onboarding rules
Open Marketplace settings. Choose the offered onboarding mode and review commission and seller policies.
- Prepare the seller agreement, prohibited-items policy, and buyer-protection information.
3. Review sellers
Open Sellers to inspect applications or use Add seller. Review each seller’s details before approval.
- Apply approval or suspension actions only to the intended seller.
4. Test the operation
Use an approved test arrangement to inspect a seller product, customer order, and the resulting commission records.
- Do not infer automatic seller payouts from a displayed commission figure.
Completion checklist
- Seller terms and onboarding rules are recorded.
- The seller-to-order workflow has been reviewed.
Troubleshooting
Why do I see a seller membership instead of operator tools?
This store may be a marketplace seller. Check the store identity and membership shown on the Marketplace page.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Linked stores: product sync and group reports
Manage a group of stores and review shared operating reports.
Illustrated guide: lulu.us.com/help/linked-stores-and-group-reports
Before you startYou need authorized access to the stores you plan to link.
1. Create or review the group
Open Linked stores. Review the group name, primary store, member stores, and country assignments.
- Use Add store only for stores that belong in this group.
2. Push selected products
Choose Push products and select a small set for the intended target store.
- Review the target and product data before confirming.
3. Inspect the sync log
Check the Sync log and inspect results. Use Re-push only after understanding the existing result.
- Verify the product in the target store; do not assume all local edits or settings are shared.
4. Review group views
Use Group inventory, Group customers, and Group margin to compare stores.
- Mixed-currency customer totals are indicative.
- Margin reports can exclude variants without unit cost.
Completion checklist
- The correct stores and countries are linked.
- A sample product is verified in the target store.
Troubleshooting
Why is a product missing from group inventory?
It may not have been synced to that store. Review product links and the sync log before pushing it again.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Campaigns: track marketing activity and attribution
Create campaign records and inspect the source of recorded sales.
Illustrated guide: lulu.us.com/help/track-marketing-campaigns
Before you startChoose consistent campaign names and tracking values before sharing links.
1. Create a campaign
Open Growth → Campaigns → Create campaign. Enter its name and the budget or tracking fields offered.
- Use source, medium, and campaign values that your team will recognize.
2. Review campaign details
Open the saved campaign and check its links and configuration.
- Creating a tracking record does not itself publish an advertisement or send a newsletter.
3. Use consistent tracking
Use the intended campaign tracking values in the links you distribute through your marketing tools.
- Test the destination URL before sharing it.
4. Review attribution
Open Growth → Attribution and compare channels and campaigns for the same period.
- Attribution is based on recorded activity and may not account for every interaction.
Completion checklist
- Campaign tracking is consistent.
- The destination and report period have been checked.
Troubleshooting
Why does a campaign show no activity?
Check that links were used, visits or orders were recorded, and the report period is correct. A campaign record alone does not generate traffic.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Bundles and comparison: help customers choose
Configure bundle offers and the product attributes used for comparison.
Illustrated guide: lulu.us.com/help/bundles-and-product-comparison
Before you startInstall the required app when prompted and prepare compatible products.
1. Create a bundle
Open Marketing → Bundles → Create bundle. Give it a name and add the products allowed by the editor.
- Review the offered discount and image before saving.
2. Preview the offer
Enable the relevant bundle component in the theme if needed. Check the storefront and add the bundle to cart.
- Confirm the actual cart discount rather than relying only on promotional text.
3. Choose comparison attributes
Open Products → Compare. Review Base fields and storefront-visible Metafields, then order the attributes.
- Choose attributes that help compare these products meaningfully.
4. Test products together
Preview the comparison experience with products that have complete values and products with missing values.
- Keep labels and units consistent.
Completion checklist
- The bundle produces the intended cart result.
- Comparison values are useful and consistent.
Troubleshooting
Why is my bundle not visible?
Check the app installation, saved bundle state, selected products, and the theme component that displays it.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Reviews and inbox: respond to customers
Moderate reviews and manage conversations from the admin.
Illustrated guide: lulu.us.com/help/reviews-and-customer-inbox
Before you startUse the correct customer or review record and follow your store’s support process.
1. Review submissions
Open Reviews and filter or search by reviewer, text, or product. Read the full review before acting.
- Use Approve or Reject according to your moderation policy.
2. Write a public reply
Enter a reply and choose Save reply when appropriate.
- Replies are public; do not include private order or contact details.
3. Open conversations
Go to Inbox and select the relevant conversation. Read its history before responding.
- Check the customer identity and channel.
4. Resolve the actual issue
Check the related order or product before making a promise. Send the response through the available conversation controls.
- Confirm the message appears in the conversation and avoid duplicate replies.
Completion checklist
- Moderation matches your policy.
- The reply addresses the correct customer issue.
Troubleshooting
Why is a review not on the storefront?
Check approval status and whether the theme or app displays reviews for that product.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
CRM, loyalty, and automations: manage retention
Review customer tasks, points, and available automation runs.
Illustrated guide: lulu.us.com/help/crm-loyalty-and-automations
Before you startCheck which retention tools are enabled for your store before promising a program to customers.
1. Review customer tasks
Open Customers → CRM. Inspect Tasks, Customer lifecycle, and Recent activity.
- Complete a task only after carrying out the underlying work.
2. Configure loyalty
Open Growth → Loyalty. Review Points program and Members. Use Adjust only with a clear reason.
- Check the intended member and point amount before confirming.
3. Inspect automations
Open Growth → Automations and read the available flow descriptions. Review Flow runs.
- Understand the trigger and customer impact before running a flow manually.
- Do not assume a waitlisted Growth feature is active.
4. Verify an outcome
Use a test customer or approved sample and inspect the resulting activity, points, or flow record.
- A run record alone is not proof of an email being delivered or a customer purchase.
Completion checklist
- Customer tasks reflect completed work.
- Points and automation outcomes have been checked.
Troubleshooting
Why is a Growth feature unavailable?
Some features can require activation or be waitlisted. Use the status displayed in your store and ask support about availability.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Subscriptions: plans and subscriber management
Configure available recurring-order plans and manage subscribers.
Illustrated guide: lulu.us.com/help/subscriptions-and-recurring-orders
Before you startInstall the Subscriptions app when prompted. Confirm supported payment and renewal behavior before selling recurring commitments.
1. Set up a plan
Open Subscriptions after installation. Under Plans choose Add plan and enter the plan name and interval.
- Use a clear schedule such as monthly delivery.
2. Choose eligible products
Use Choose products or the available all-products option. Review the products before saving.
- Check stock and delivery requirements for repeated orders.
3. Review subscriber actions
Under Subscribers inspect a test subscription. Use Pause, Resume, or Cancel only for the intended subscription.
- Record a reason when canceling.
- Review Notifications for customer communication.
4. Know how renewals are shipped
Each renewal keeps the shipping method of the subscriber's last order, so a customer who chose Express keeps paying Express. If that method no longer qualifies (for example its weight or order-value condition is no longer met), the renewal uses the first shipping rate that does qualify for their address, and failing that your first configured rate for that destination.
5. Test before launch
Confirm the storefront plan selection and the actual renewal and payment workflow with support or an approved test.
- A saved recurring plan does not prove an external gateway supports automatic recurring charges.
Completion checklist
- The plan has the intended interval and products.
- Renewal and cancellation behavior are understood.
Troubleshooting
Why can’t I find Subscriptions controls?
Install the required app and confirm access. If payment renewal support is unclear, resolve it before offering the plan.
Why did a renewal ship with a different method than the first order?
A renewal reuses the shipping method of the subscriber's last order when it still qualifies for the address and cart. If you changed or removed that rate, or its conditions no longer apply, the next qualifying rate is used.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Auctions, preorders, and offers: launch an optional selling tool
Find the setup sequence for app-based selling methods.
Illustrated guide: lulu.us.com/help/advanced-selling-apps
Before you startCheck the app listing and activation status. Availability and limitations vary by tool.
1. Choose the app
Open the App Store and review the relevant auction, presale, or offer app. Read its supported features and requirements.
- Separate available functionality from planned capabilities.
2. Configure the module
After installation, open Auctions, Presale, or Offers as appropriate. Review its Settings before creating a listing, campaign, or rule.
- Set timing, eligible products, and the transaction rules exposed by that editor.
3. Review customer messaging
Enable the appropriate theme component and explain the selling terms in customer-facing content.
- For preorders, communicate expected fulfillment.
- For auctions or offers, explain how a purchase is completed.
4. Test and monitor
Run a controlled test of the customer action and resulting order. Review the module’s orders, bidders, analytics, or reports as applicable.
- Do not begin a live event until timing, payment, and fulfillment have been verified.
Completion checklist
- The tool is installed and its settings reviewed.
- A controlled end-to-end test has succeeded.
Troubleshooting
Why does the installed app not appear on the storefront?
Review its theme-block requirements and activation status. Installing an app does not automatically publish every component.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Wise AI: assistant, credits, and discovery
Find AI tools and review their output and usage.
Illustrated guide: lulu.us.com/help/ai-assistant-and-credits
Before you startConfirm which AI tools and credit balance are available to your account.
1. Review Wise AI
Open Wise AI to inspect available tasks and the monthly credit balance.
- Read the current usage and feature requirements before starting a task.
2. Ask the assistant
Open Wise Assistant and describe the task clearly. Include a product or order reference when useful.
- Review proposed changes before confirming actions.
- Check generated copy for accuracy.
3. Manage usage
Open Wise AI credits to inspect history and available purchase options. Read the amount and currency before confirming a purchase.
- Keep billing confirmations and avoid duplicate purchases after a delayed response.
4. Review discovery
Open Agentic to inspect discovery, listing quality, and search preview. Review SEO & AI separately for crawler access.
- A discovery score or preview does not guarantee an external AI recommendation.
Completion checklist
- AI output is reviewed before use.
- Credit usage and discovery settings are understood.
Troubleshooting
Why did an AI task not finish?
Check the available credits, the displayed error, and whether the feature is enabled. Do not repeat a paid action until you have checked its outcome.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Installments and BNPL: configure eligible payment options
Review provider connections and bank installment plans.
Illustrated guide: lulu.us.com/help/bank-installments-and-bnpl
Before you startYou need the provider’s merchant approval and supported currency. Confirm commercial terms directly with the provider.
1. Review payment providers
Open Settings → Payments. Inspect the available buy-now-pay-later provider controls.
- Use credentials for the correct merchant account and environment.
2. Configure a connection
Enter the requested fields for an approved provider and save. Follow the provider-specific setup instructions supplied for your account.
- Keep secret keys private.
- Ask support if a required callback or environment setting is unclear.
3. Review bank plans
Open Easy payment plans when available. Add a provider and review its tenors and other plan fields.
- Enter only the installment terms your business is authorized to offer.
4. Test eligibility and reporting
Test an eligible checkout and confirm the payment outcome. Use Payment plan reports to review provider and tenor activity.
- A displayed installment choice does not establish provider approval or guarantee settlement.
Completion checklist
- Provider approval and store configuration agree.
- An eligible checkout and its payment record have been verified.
Troubleshooting
Why is a payment option missing at checkout?
Check activation, currency, order eligibility, and merchant credentials. Ask support to inspect the configuration without sending secrets through public messages.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Troubleshooting: missing products, checkout, and support
Work through common issues and give support the details needed to investigate.
Illustrated guide: lulu.us.com/help/troubleshoot-store-problems
Before you startNote the store address, affected page, and approximate time of the problem.
1. Confirm the context
Check which store and account you are using. Refresh once and compare the public page in a private browser window.
- Record the exact error message.
- Check whether the issue affects one device or all devices.
2. Check the relevant settings
For missing products, inspect status, stock, collections, and theme visibility. For checkout, inspect payment, shipping coverage, and required fields.
- For a missing admin action, check staff permissions and app activation.
3. Avoid repeating sensitive actions
For payments, refunds, order submissions, or imports, inspect the existing result before retrying.
- A delayed screen response does not prove that the action failed.
4. Contact support with evidence
Use the help contact option. Include the store address, page, steps to reproduce, expected result, and an anonymized screenshot.
- Exclude passwords, API keys, gift-card codes, private preview links, and customer payment details.
Completion checklist
- You have identified a repeatable issue or its resolution.
- Support has a clear description without secrets.
Troubleshooting
What should I send if I cannot reproduce it?
Send the approximate time, browser and device, affected order or product reference, and what happened immediately before the issue. Avoid sharing sensitive customer information.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Theme editor: sections, blocks, and templates
Build page layouts, edit their content, and preview each screen size.
Illustrated guide: lulu.us.com/help/theme-editor-sections
Before you startWork on a duplicate draft theme when you want to keep a redesign off the live store.
1. Open the right theme
Go to Online Store → Themes and open the editor for the theme you intend to change. Confirm its name and whether it is live or draft.
- Use the theme actions to Duplicate first if you need a safe working copy.
- Changes saved to the live theme can affect customers.
2. Select a template
Use the template selector at the top of the editor to choose the home page or the relevant product, collection, page, or article template.
- Use New template when you need a separate layout supported by the selector.
- Preview a representative resource for that template.
3. Edit sections and blocks
In Sections, select an existing section to open its inspector. Edit its text, media, products, or other supported fields. Use Add section to insert another section.
- Use reorder controls to change the page sequence.
- Open a section’s blocks to add or reorder supported items.
- Hide an element to test a layout before deciding to remove it.
4. Review header and footer
Open Header or Footer in the section tree. Review navigation, branding, and the footer builder controls.
- Use Content → Menus to change the linked menu’s items.
- Check long menu labels on mobile.
5. Preview and save
Switch between desktop and mobile previews, then Save. Use Undo or Redo to correct recent editor changes.
- Ctrl/Cmd+Z undoes; Ctrl/Cmd+Shift+Z redoes.
- Check that the Saved confirmation appears.
- Open the storefront preview to test links, product selection, and cart behavior.
Completion checklist
- The correct template contains the intended sections.
- Both mobile and desktop previews have been checked.
- Your changes show a saved confirmation.
Troubleshooting
Why does the page I’m viewing not change?
Confirm the theme, template, and preview resource. You may be editing a draft or an alternate template that the page does not use.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Theme editor: colors, fonts, and app embeds
Adjust global appearance and enable installed app components.
Illustrated guide: lulu.us.com/help/theme-editor-brand-and-apps
Before you startInstall the app before expecting its embed or block to appear in the theme editor.
1. Open Theme settings
In the theme editor select Theme settings. Review the available color, typography, layout, and other controls.
- The available tokens and controls depend on the theme.
- Use consistent text and background colors with readable contrast.
2. Check global and local styling
Change a setting, then preview several templates. A section can have its own settings in addition to global theme settings.
- Check buttons, links, headings, and form fields.
- Use the mobile preview to catch wrapping and cramped layouts.
3. Enable app components
Choose Apps in the editor to review available embeds. Enable and configure the relevant installed component. For an app section, use the supported section or block picker.
- Not every app has a storefront component.
- An installed app can still need its own configuration.
4. Save and test
Save the theme and test the customer action provided by the app, such as adding a bundle to cart.
- Confirm the app’s plan and usage limits in the app itself.
- If you remove an app, recheck pages that used its component.
Completion checklist
- Global styles are readable on multiple templates.
- Enabled app components work in the storefront.
Troubleshooting
Why is my installed app missing from Apps?
The app may not supply an embed, may require another type of theme section, or may need activation. Review its setup guide and listing requirements.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Theme code: custom CSS, JavaScript, and version history
Use the supported code files and restore a saved theme version.
Illustrated guide: lulu.us.com/help/theme-code-and-history
Before you startUse a draft theme and download a backup before editing code. JavaScript and head snippets require owner or admin access. On a premium theme you haven't bought, custom.js and head-snippets.html are read-only and GitHub sync is off until you buy it. Custom CSS still works.
1. Open Edit code
In the theme editor choose Edit code. Select the file you intend to inspect.
- custom.css adds storefront styles.
- custom.js runs on storefront pages after loading.
- head-snippets.html supplies supported head tags.
- settings.json and sections.json are read-only views; edit those through Theme settings and Sections.
2. Make one focused change
Edit only the supported file for the task. Use the admin’s Developer docs for current tokens, section schemas, and file limits.
- Keep media, fonts, and scripts on your own hosted paths.
- Do not paste secrets or private customer data into storefront code.
- Adding a file name does not create an arbitrary server-side feature.
3. Save and verify
Save and inspect the preview on desktop and mobile. Test navigation, forms, cart, and the component affected by the change.
- If the save reports a conflict, reload and reconcile the newer changes rather than overwriting blindly.
4. Use version history
Open the editor’s version-history control, review the saved versions, and restore the intended version when appropriate.
- Restoring changes the theme state. Verify the target and preview afterward.
- Keep a downloaded package for an additional recovery point.
Completion checklist
- The code saves without errors.
- The affected customer journey still works.
- You know which version or package to recover from.
Troubleshooting
Why can’t I edit settings.json directly?
It is a read-only view. The supported settings and section editors validate the values before saving them.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Theme packages: download, upload, and publish
Move a Lulu theme package into a draft and publish after review.
Illustrated guide: lulu.us.com/help/theme-packages-import-export
Before you startUse a Lulu export, not a generic Shopify Liquid ZIP. Review paid-theme licensing before publishing.
1. Download a working copy
Open Online Store → Themes, open the theme’s actions menu, and choose Download theme file. Keep the ZIP unchanged as a backup.
- The package contains a canonical shopwise-theme.json file.
2. Import a package
In Themes choose Import and select the upload option. Upload the Lulu ZIP or shopwise-theme.json file, within the 5 MB limit.
- The importer reads shopwise-theme.json and the copies of the same data in the ZIP: config/settings_data.json, templates/*.json (including alternate templates such as page.contact.json), config/groups.json and assets/custom.css.
- A copy you edited is used in place of the matching part of shopwise-theme.json. A copy you didn't touch changes nothing. If you change the same part in both places, shopwise-theme.json wins. After the import, a note on the Themes page lists the files whose edits were used and anything that was left out, such as unknown section types, settings or presetKey.
- sections/*.json, the README files, assets/custom.js and snippets/head-snippets.html are never read back. Change custom JavaScript and head snippets in shopwise-theme.json (codeFiles).
- Packages downloaded before 9 October 2026 have no file fingerprints, so only shopwise-theme.json is used. Download the theme again before editing the separate files.
3. Inspect the draft
Open the imported draft in the editor. Review its media references, menus, product selections, templates, and code.
- A package carries links to images, not the image files. Images uploaded to another store only show on that store, so upload them in this store and choose them again in the editor. Images on a public https:// address show everywhere.
- Theme import does not import your complete product catalog or orders.
4. Publish after testing
Use the theme’s Publish action after checking the draft. Complete any required paid-theme purchase shown by the interface.
- Confirm the live theme name afterward.
- Keep the previous theme available if you need to switch back.
Completion checklist
- The imported draft matches the intended design.
- Referenced content exists in the target store.
- The intended theme is marked live after publishing.
Troubleshooting
Why is a Shopify ZIP rejected?
Lulu requires its own canonical shopwise-theme.json package data. A plain Liquid theme export is not a supported import; ask support about adapting the design.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Apps: permissions, updates, and uninstalling
Manage installed apps and review changes before updating.
Illustrated guide: lulu.us.com/help/manage-app-updates-and-uninstall
Before you startUse an account with app-management and billing permissions.
1. Review an installed app
Open Apps and select the installed app. Inspect its functional status, plan, and usage limits.
- Confirm whether you are looking at the installed version or the public listing.
2. Configure the app
Open its settings and complete the listed requirements. If it has a storefront component, enable it in the theme editor.
- Use the app’s setup guide and test with a small sample.
3. Review an available update
If an update is offered, inspect the release details and any requested permission changes before approving it.
- Existing stores may stay on their pinned app version until the owner updates.
- Retest the affected storefront flow after updating.
4. Uninstall deliberately
Use the app’s uninstall action and read the confirmation. Review the theme and any separate external subscription afterward.
- Keep exports or records you need before removing access.
- Confirm billing terms rather than assuming all external charges stop.
Completion checklist
- The app configuration and access are understood.
- An update or uninstall has been tested in the storefront.
Troubleshooting
Why did the public app listing change but my installed app did not?
The store can remain on a pinned version. Review the installed app’s update controls and release details.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: account, dev stores and client transfer stores
Apply for a partner account, sign in once it is approved, and create a dev store to build and test in, or a client transfer store to build a store for a client.
Illustrated guide: lulu.us.com/help/partner-account-and-development-stores
Before you startPartner accounts are separate from merchant admin access. Use a business email you control. Applying is free, but every application is approved by hand by the Lulu team before you can sign in; each theme or app you publish is reviewed separately.
1. Apply for a partner account
Open partners.lulu.us.com and select the Create account tab. Enter Your name or company, your email and a password of at least 8 characters, then select "Apply for a partner account". A green "Application received" banner confirms it.
- The name you enter is shown to merchants as the maker of your listings.
- Your account stays pending until the Lulu team approves it, usually within one to two business days. You are not signed in yet; the decision arrives by email.
- Signing in before approval shows a notice that your application is still under review.
- If the email is already registered the form says so on the email field. Use Sign in instead.
- One partner account covers both themes and apps.
2. Sign in after approval and open the dashboard
When the approval email arrives, sign in at partners.lulu.us.com. You land on the Dashboard, which lists Onboarding profile, Client stores, Stores and Your submissions. The top bar links to Dashboard, Onboarding profile, Packages, Work, Leads, Listings and Reviews.
- Submissions you have not sent yet stay in Draft and are private to you.
- Onboarding profile, Packages, Work and Leads are for partners who also offer store-setup services to merchants.
3. Create a dev store or a client transfer store
Under Stores choose Create store and pick the store type. Choose Dev store to build and test themes and apps, then pick its Plan features (Basic, Grow, Advanced or Plus). Choose Client transfer store to build a store for a client; it has Advanced plan features, and you can tick "Enable Plus features". Enter a Store name of 2 to 60 characters and choose Create. The store address is derived from the name, for example aurora-sandbox.lulu.us.com.
- Both types are real Lulu stores with search and AI crawlers off. A dev store gets a sample catalog.
- Both are always password-protected (the password can't be turned off) and take test orders only: no real payments, gift cards or store credit.
- A dev store can't go live and can't be transferred. You can have up to 250.
- A client transfer store goes live only after you transfer it with "Transfer to client" and the client accepts. You can create as many as you need.
- Every partner store created before 30 October 2026 is now a client transfer store.
- Paid app plans are free here only if they are free plans, marked "Free for partners", or (on dev stores) your own app. Other paid plans show "Not free on partner stores"; the store owner picks them after the transfer.
- Storage is the Basic plan's: 100 GB of files, 50 GB of video, and 250 videos and 3D models.
- Use demonstration products and customer details only.
- Creating a partner store does not publish anything to the public Theme Store or App Store.
4. Open the store admin
Choose Preview to open the storefront, or Open admin to open the store admin. Open admin is a signed single-use handoff, so you never type a store password.
- You enter as a Collaborator on that store, not as its owner.
- The admin opens at admin.lulu.us.com/store/<handle> with the standard navigation.
- If a store owner suspends your collaborator access, Open admin returns an error instead of restoring it.
- On your own dev stores and client transfer stores you have full access until the hand-over.
- After a client accepts a transfer, your access is the collaborator default and the new owner chooses what you can do. The default has no customer export, order export or store backup export.
Completion checklist
- Your partner application was approved and you can sign in to the partner dashboard.
- A dev store or client transfer store exists and its admin opens from the dashboard.
Troubleshooting
I applied but I cannot sign in.
Your application is still under review. The sign-in form shows an under-review notice after a correct password. Wait for the approval email; contact Lulu support with your partner email if nothing arrives within two business days.
Why is the portal showing a provisioning or access notice?
The partner service is not ready on that environment. Follow the notice and contact support with your partner email if it persists.
Why was my dev store refused?
You can have up to 250 dev stores. Delete dev stores you no longer need, or reuse one. Client transfer stores have no limit.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: upload and submit a theme
Send a theme package or development-store snapshot to Lulu for review.
Illustrated guide: lulu.us.com/help/partner-upload-theme
Before you startHave a tested Lulu theme, listing copy, a price in USD, and the rights to distribute the design and its assets.
1. Start a theme submission
On the dashboard choose New submission and keep the Theme tab selected.
- Drafts stay private to you until you send them for review.
2. Choose the source
Select From a development store and choose the Development store and the Theme, or select Upload a file and choose the package.
- A development-store selection is snapshotted at save time; later edits in that store do not change the submission.
- Upload accepts a Lulu export zip or a bare shopwise-theme.json, up to 5 MB.
3. Complete the listing details
Enter Theme name (up to 120 characters), Tagline (up to 200), Industries and Price (USD).
- Industries is comma-separated, up to ten entries.
- Price is stored as whole cents. Enter 0 to propose a free theme.
- There is no screenshot, description or feature field on this form; those are filled in on the listing editor after approval.
4. Check the validation feedback
If the file is not a Lulu package the submission is refused and nothing is saved. The banner names the problem, for example that the file is not a Lulu theme export.
- Fix the file and try again; a refused upload does not leave a draft behind.
5. Save or submit
Choose Save draft to review the submission first, or Save and submit for review to send it. Either action opens the submission detail page.
- Reviewers see your listing fields plus a summary of the package: the theme name inside it, how many settings it carries, and whether sections and custom code are included.
- Confirm the theme summary, name and proposed price before sending.
Completion checklist
- The submission contains the intended theme snapshot or package.
- Listing name, tagline, industries and price have been checked.
- You know whether the submission is still a draft.
Troubleshooting
Why did my later theme edit not appear in the submission?
The submission captured a snapshot when it was created. Later development-store edits do not modify it. Send a new submission with the corrected theme.
Why was my upload refused?
The import reads shopwise-theme.json from a Lulu export. A Shopify Liquid archive, an unrelated zip, or a file over 5 MB is rejected with a message naming the reason, and no draft is created.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: edit a theme listing and release an update
Update listing content, publish a new package, and tell merchants what changed.
Illustrated guide: lulu.us.com/help/partner-edit-theme-listing
Before you startUse the partner account that owns the listing. Saves are live immediately and are not re-reviewed.
1. Open the listing editor
In the partner portal open Listings, stay on the Themes tab and choose Edit on your theme. View opens the public listing page.
- The Type column shows whether a row is a partner listing or a built-in Lulu theme.
- The Visibility column shows Listed or Unlisted.
2. Update the listing copy
Review Name, Tagline, Description, Industries, Features and Screenshot URL, then Website, Price (USD, one-time) and Visibility.
- Industries are chips; click to toggle. Features is comma-separated.
- Screenshot URL takes an https:// URL or a /media path. Host your imagery yourself.
- Visibility switches between Listed and Unlisted.
- Price is a one-time USD amount; Lulu sells and bills every Theme Store listing and credits you as the maker.
3. Record the release
Fill in Version, Release date, Documentation URL, Changelog, Support email and Support URL, then choose Save changes.
- Version uses a number such as 1.2.0.
- Changelog takes one entry per line in the form version | date | what changed, up to thirty entries.
- This block is what a merchant reads on the listing page before installing, and it is the only place an existing merchant learns what changed.
4. Replace the published package
Under Theme package use Download to keep a copy of the current package, then either Upload zip with a tested export, or pick a store under Edit in development store and choose Open editor to work on it in the real editor.
- Open editor installs the published package on your dev store as a fresh draft and signs you in to the editor.
- Opening the editor alone releases nothing.
5. Publish the edited theme back
Under Update from development store choose the store and the theme you edited, then choose Update listing. The package is rebuilt on the server from that theme.
- Saving listing copy and replacing the package are separate actions.
- A theme package has no stored release history and no rollback, so download the current package before replacing it.
6. Check how merchants receive it
Install the theme fresh in a dev store and confirm the update is there.
- A package change affects new installations only.
- A merchant who already installed the theme owns a copy inside their own store; Lulu never overwrites it or their customizations.
- Version and changelog are how existing merchants find out there is something newer.
Completion checklist
- Listing copy, version and changelog match the release.
- A fresh installation contains the update.
- You have a copy of the package you replaced.
Troubleshooting
Why didn’t an existing merchant theme change?
Installed themes are copies owned by each store. A package update reaches new installations; it is not an automatic overwrite of existing copies.
Why can’t I edit the price on this row?
Built-in Lulu catalog themes have their pricing defined in the product itself, so the price field is refused on those rows. Only standalone partner listings set their own price.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: submit an app listing
Propose an app for the App Store and understand the current integration boundary.
Illustrated guide: lulu.us.com/help/partner-submit-app
Before you startPrepare an accurate description of the working integration and its requirements. The portal accepts listing proposals, not executable app packages.
1. Start an app submission
From the dashboard choose New submission, then switch the type selector to App.
- If only Theme is offered, ask Lulu support about app submission access on your account.
2. Describe the app
Fill in App name, Tagline, Category, Pricing tag and Description. All five are required.
- App name up to 120 characters; Tagline up to 200; Category and Pricing tag up to 80; Description up to 5,000.
- Category is free text, for example Marketing, Shipping or Store design.
- On the published listing the pricing tag is shown as one of four labels: Free, Free plan available, Free to install, or Free trial.
- Say what the app does, who it is for, what store data it reads and writes, and what a merchant needs in place before it works.
3. Declare permissions and data access in writing
There is no code, package, callback URL, scope or billing-plan field on this form, and no partner endpoint accepts an executable upload. State the permissions and data access your app needs in the Description and agree them with the Lulu team.
- Permissions shown on the merchant's install consent screen, billing plans and theme-editor embeds are configured by Lulu.
- Do not upload app code as a theme package.
- Submitting a description does not deploy or run anything.
4. Save or submit
Choose Save draft to review the proposal, or Save and submit for review. Follow the status and reviewer notes on the submission detail page.
- A submitted proposal is locked during review.
- Approval inserts the listing into the App Store, owned by your partner account.
5. Validate before you promote it
Once the implementation and the listing are live, install the app in a dev store and test configuration, permission prompts and the customer journey end to end.
- Every plan of your own app is free on your dev stores, so you can test paid plans without being charged.
- Do not advertise a capability that only exists in the listing text.
Completion checklist
- The proposal accurately describes the app and the data it touches.
- Implementation, permissions and plans have been agreed with Lulu.
- The review status and next step are clear.
Troubleshooting
Where do I upload my app code?
Nowhere in the partner portal. It accepts listing proposals only. Submit the proposal and coordinate the technical integration with Lulu support. Theme upload is for themes.
How do I set my app's scopes or billing plans?
Not from the portal. Scopes, plans and embeds are configured by Lulu and are not editable in the partner listing editor either. Agree them with the Lulu team.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: edit app listings and restore versions
Maintain app information and support links, and roll a listing back to an earlier release.
Illustrated guide: lulu.us.com/help/partner-edit-app-listing
Before you startUse the partner account that owns the app. Listing edits become public immediately.
1. Open the owned app
Go to Listings, switch to the Apps tab and choose Edit on the app. Review Name, Tagline, Description, Category, Pricing and Icon.
- Pricing is a four-way selector: Free, Free plan available, Free to install, or Free trial. A pricing label does not configure a billing plan.
- Icon takes an emoji, an https:// URL or a /media path. Host your icon yourself.
2. Maintain the support information
Fill in Website, Support email, Support URL, Privacy policy URL and Documentation URL.
- Every URL must start with https://.
- These appear in the support block on the public listing and in the merchant's admin.
- Open each destination and check it before saving.
3. Save a release
Choose Save changes, then open the public listing to check the result. Every save is recorded in Version history, newest first.
- The public App Store reads this row directly, so an edit is live as soon as it saves.
- This editor does not change app scopes, billing plans, embeds or executable code; coordinate those with Lulu.
4. Restore an earlier version
In Version history find the release you want and choose Restore on it. Restore is offered on every entry except the newest.
- Restore copies that version's values back and records the result as a new release called “Restored from v<n>”; history is appended to, never rewritten.
- Stores stay on the version they are pinned to until their owner updates the app, so a restore is not a mass rollback.
Completion checklist
- Public listing details and links are correct.
- The new release appears in version history.
- You know which changes need Lulu to make them.
Troubleshooting
Will restoring an app listing roll back every store?
No. Restore creates a new version of the listing; installed stores keep their pinned version until they update. It is not a mass rollback of merchant installations.
Why is there no Restore button?
Restore is not offered on the newest release, because that is the one already live. A listing with only one release therefore shows no Restore button.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: reviews and merchant collaborator access
Answer marketplace reviews, ask for one, and get access to a merchant store.
Illustrated guide: lulu.us.com/help/partner-reviews-and-collaborator-access
Before you startReplies are public and show your partner account name. Get the merchant's agreement before asking for store access; collaborator access is requested from the merchant's lead under Leads.
1. Read your reviews
Open Reviews in the partner portal and switch between the Apps and Themes tabs. Reviews are listed newest first with the store name, rating and date.
- Only merchants who installed your app, or have your theme in their library, can write one.
2. Reply in public
Use the reply control on a review. The reply appears under that review on the App Store or Theme Store with your account name, and can be edited later.
- Keep the reply about the issue raised.
- Never include customer data, order details or credentials in a public reply; move private troubleshooting to your support channel.
3. Ask a merchant for a review
In Request a review choose the Listing, enter the merchant's email address in To, add Your name and an optional Message, then choose Send request. They receive a link to the review form.
- Send it to a merchant you already work with.
- They can only write a review if they actually have the app installed or the theme in their library.
4. Get collaborator access to a merchant store
Ask the merchant for the 4-digit collaborator request code from their admin under Settings → Users → Collaborators. In the partner portal open Leads, open that merchant's lead, enter the code as "Collaborator request code" (with an optional message) and select "Request access". Once the merchant approves, the store appears under Client stores on your Dashboard with an "Open admin" button.
- You enter as a Collaborator, not as the owner.
- The merchant can also grant you access directly from Onboarding partners → My requests in their admin.
- The merchant can suspend or remove that access at any time, and a suspended collaborator cannot re-enter.
- Your own dev stores and client transfer stores need none of this — they are already yours.
- Default access does not include exporting customers, exporting orders or exporting a store backup. Ask the store owner to turn on what the job needs under Settings → Users → Collaborators → "Edit access".
- Without the matching export permission you can't create an API token or a webhook that reads customers or orders in that store.
- After 5 wrong codes for a store, new requests to that store are locked for 60 minutes and the store is told by email.
5. Work within the approved scope
After approval, confirm which store you are in and which actions your role allows. Make design changes on a draft theme and agree the release with the merchant.
- Ask the merchant to remove your access when the engagement ends.
- Access you do not use for 90 days is removed automatically. You get a warning email after 75 days. Open the store admin from your Dashboard to keep it.
- The store owner can see the changes you make, under Settings → Activity.
Completion checklist
- Review replies contain no private data.
- Merchant access is explicitly approved and limited to the task.
Troubleshooting
Why can’t I open a merchant’s admin?
Open the store from Client stores on your Dashboard. If it is not listed or Open admin shows an error, the collaborator access may be pending, suspended, or may lack the permissions the task needs. Ask the store owner to review it under Settings → Users.
My access to a store has expired.
You did not open that store for 90 days, so the access was removed. Ask the store owner to give it back under Settings → Users → Collaborators, or send a new request with their current request code.
My request code is refused with "No store matches that address and code".
The address or the code is wrong, or requests to that store are locked for 60 minutes after 5 wrong codes. Ask the merchant for the current code and try again later.
Why did my review request fail?
The address must be a valid email and the form is rate limited. Check the address, wait a moment and try again; contact support if it keeps failing.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
POS: scan products and take payment
Build a register cart, record tender, and provide a receipt.
Illustrated guide: lulu.us.com/help/pos-complete-a-sale
Before you startUse a paired device, authorized staff PIN, open drawer session, and configured payment types.
1. Open the register
Enter the register through Point of Sale and sign in with the authorized staff access. Confirm the register and location.
- Verify you have an active session and the intended inventory location.
2. Build the cart
Search or scan a product barcode, choose the correct variant, and set the quantity. Add the customer if needed.
- Review item prices and supported discounts before checkout.
- Use saved-cart controls when parking a sale, rather than marking an unpaid sale as paid.
3. Review checkout
Choose the checkout action and inspect the total, tax, discount, and required customer information.
- Complete any required contact details before taking payment.
- Review tipping if it is configured.
4. Record the tender
Select an enabled payment type. For cash, enter the amount tendered and check the change. For split payment, record each portion until the balance is covered.
- For card or custom tender, confirm actual external payment success before recording it.
- A register tender entry is not proof that a bank or terminal charged the card.
5. Finish and receipt
Complete the sale and use the receipt controls to provide the receipt. Review the resulting order if anything is unclear.
- Do not repeat a payment after a slow response until you check the order and provider outcome.
- Use email or print receipts where available. SMS receipts are not currently connected to a gateway.
Completion checklist
- The sale has the correct products and customer.
- Tender covers the total and cash change is correct.
- The receipt and order record exist.
Troubleshooting
Why is there still a remaining amount?
A partial or split tender has not covered the total. Check the amounts already recorded before adding the remaining payment.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
POS: returns, refunds, and exchanges
Return items against an order or exchange them through the register.
Illustrated guide: lulu.us.com/help/pos-returns-and-exchanges
Before you startFollow the store’s return policy and use the required manager approval when prompted.
1. Find the original order
Open register Orders and find the receipt or order. Start the return or exchange flow for the correct transaction.
- Check which quantities were already refunded or returned.
2. Select return items
Choose the items and quantities, and review restocking options and the calculated refund.
- Restock only items that should be sellable again.
- Use the unverified-return flow only when your permissions and policy allow it.
3. Choose the refund destination
Review the offered destinations and amounts. An unverified return is limited to gift card or store credit.
- For an original-payment refund, verify the provider result.
- Keep newly issued gift-card codes private.
4. Exchange if appropriate
Use the exchange action to carry the return value into a replacement sale. Add the replacement items and review the balance at checkout.
- The exchange is completed at checkout; parking it does not finish the transaction.
5. Confirm and reconcile
Complete any manager approval, confirm once, and inspect the receipt, order, stock, and payment outcome.
- Provide the appropriate return or gift-card receipt.
Completion checklist
- Return quantities and destination are correct.
- Replacement items and any balance are settled.
- Stock and payment records agree.
Troubleshooting
Why can’t an unverified return go back to a card?
Without the original verified order, the available destinations are restricted to gift card or store credit. Follow the store’s policy and approval process.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
POS: offline sales and synchronization
Understand queued sales and resolve sync problems after reconnecting.
Illustrated guide: lulu.us.com/help/pos-offline-sales
Before you startReview POS Settings → Offline sales and the allowed payment types and limits before relying on offline operation.
1. Check offline readiness
Use the paired register and review the connection indicator. Ensure the items and access needed for selling are available on the device.
- Offline operation has limits and is not a substitute for provider authorization.
2. Use only permitted options
When offline, follow the payment options and limits exposed by the register.
- Do not assume online-only card authorization works without a connection.
- Keep the device and its browser data intact while sales are queued.
3. Reconnect and inspect
When connectivity returns, open Offline sales and inspect queued records. Use Retry or the retry-all action as appropriate.
- Check each result; a local sale is not synchronized until the server accepts it.
4. Resolve exceptions
Compare any failed record with the actual order list and payment outcome before repeating it. Discard only when the sale truly should be removed and complete manager approval if requested.
- Discarding a queued record is not a refund.
- Contact support before clearing browser storage with unsynchronized sales.
Completion checklist
- All intended sales have synchronized.
- Failed entries have been reconciled rather than duplicated.
Troubleshooting
Why is Retry unavailable?
The device may still be offline, a sync may already be running, or there may be no queued records. Check the connection and current status.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Dropshipping: supplier returns and reconciliation
Coordinate supplier return status with the customer order and refund.
Illustrated guide: lulu.us.com/help/dropshipping-returns-and-reconciliation
Before you startDropshipping must be enabled. Agree the supplier return process before accepting customer returns.
1. Find the customer order
Open the affected order and confirm the purchased variant, supplier reference, delivery state, and customer issue.
- Determine whether the issue is cancellation before dispatch or a return after delivery.
2. Agree return handling
Check the supplier’s requirements and contact the supplier through the agreed process. Give the customer only confirmed return instructions.
- Verify the return destination and any authorization reference.
- Do not promise a supplier reimbursement before it is approved.
3. Track the supplier return
Open Dropshipping returns when available and inspect the relevant record. Use only the next-state actions offered for its current status.
- The module must be enabled before records and transitions are available.
- Keep supplier correspondence with your operational records.
4. Handle the customer refund
Use the customer order’s refund workflow separately when appropriate. Verify the refund outcome and restocking decision.
- A supplier return status is not automatically a customer payment refund.
- Do not restock a supplier-held item as local warehouse stock.
5. Reconcile the costs
Compare customer refund, supplier credit, shipping costs, and the original order totals.
- Record unresolved supplier reimbursement and investigate differences before closing the case.
Completion checklist
- Supplier return status and customer communication agree.
- Customer refunds and supplier credits are reconciled separately.
Troubleshooting
Why did changing a return status not refund the customer?
Supplier-return tracking and the customer payment are separate workflows. Check the order refund controls and payment-provider outcome.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Dropshipping hub: wholesale price lists
Publish a supplier catalog for eligible external retailers.
Illustrated guide: lulu.us.com/help/dropshipping-wholesale-price-lists
Before you startThis is the supplier or hub workflow. Dropshipping must be enabled and the variants must already exist.
1. Create a list
Open Dropshipping price lists → Create price list. Enter Name, Visibility, and Currency.
- Private and Public (any eligible retailer) have different audiences.
- Set currency explicitly to avoid ambiguity.
2. Add a variant
Choose Manage items for the intended list, then Add item. Enter the Lulu Variant ID.
- Use the variant identifier, not the parent product ID or supplier SKU.
- Ask your integration contact to confirm identifiers if they are not clear.
3. Enter wholesale pricing
Fill in Wholesale (cents) and optional MAP (cents).
- These fields accept integer cents: for USD 12.50 enter 1250.
- MAP means minimum advertised price; use it only where appropriate to your supplier agreement.
4. Review retailer access
Save the item, review the list’s displayed amounts and currency, and test access through an authorized retailer integration.
- A public list is intended for eligible retailers; it is not proof that an external connection has been configured.
Completion checklist
- Variant identifiers and currency are correct.
- Displayed amounts match the intended wholesale prices.
- The intended retailer can access the configured catalog.
Troubleshooting
Why is my price one hundred times too small?
The entry fields are labeled cents. Check whether you entered whole currency units instead of integer cents, then correct the intended item through the supported management or support process.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Dropshipping hub: API keys and retailer access
Create scoped access for an external store and revoke it when no longer needed.
Illustrated guide: lulu.us.com/help/dropshipping-hub-api-keys
Before you startDropshipping must be enabled. Agree the integration and minimum required access with the retailer or developer first.
1. Create an identified key
Open Dropshipping API keys → Create API key. Give it a name identifying the retailer or integration.
- Use a separate key for each connection so access can be revoked independently.
2. Choose scopes
Select only the required scopes: catalog:read, inventory:read, orders:write, orders:read, or fulfillments:read.
- Read scopes retrieve the named information.
- orders:write permits order-writing operations and should be granted deliberately.
3. Store the one-time secret
Create the key, copy the secret from Copy your new key now, and store it in the integration’s secret storage.
- The full secret is shown once and cannot be retrieved later.
- Do not place it in storefront JavaScript, screenshots, email, or a public repository.
4. Test and monitor
Have the authorized integration test its connection. Review Prefix, Scopes, Rate/min, Last used, and Status in the key list.
- A created key alone does not implement the external integration.
5. Revoke access
Use Revoke for an obsolete or exposed key. If replacing a key, configure and test the new one before revoking the old one when operationally appropriate.
- Revocation stops the integration using that key; coordinate the change with its owner.
Completion checklist
- The key has only the intended scopes.
- Its secret is stored privately.
- An authorized connection has been tested.
Troubleshooting
Can I view the secret again later?
No. Create a replacement key if the secret was lost, configure the integration with it, and revoke the old key.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Pay for your package
Pay for your package at signup, upgrade or downgrade under Change package, and understand how renewals work.
Illustrated guide: lulu.us.com/help/pay-for-your-package
Before you startPackages are billed in USD: Basic $20, Grow $50 or Advanced $290 a month, or $17, $45 and $250 a month on yearly billing; Plus starts at $1,950 a month by agreement. There is no free package: the first billing cycle is paid during signup and your store is created only when that payment goes through. You need the store owner or billing permission to change or cancel the package.
1. Open Settings > Billing
Click Settings at the bottom of the sidebar, then Billing. The top card shows your current package, whether it is Active, the renewal date and the platform transaction fee. The Usage card shows products, orders and staff against your package limits, and Past bills lists every package payment with "Download".
2. Upgrade or downgrade under "Change package"
Click "Upgrade" or "Downgrade" next to another package; yours is marked "Current". Upgrading applies straight away and charges only the difference for the days left in the cycle. Downgrading takes effect on your renewal date and shows what it removes before you confirm; you keep everything you paid for until then. Plus is a custom agreement arranged with the team.
3. Pay in the secure payment window
When a payment is due, the secure payment page of the platform's card payment provider opens. Pay by card there; Lulu never sees or stores your card number. Nothing changes until the payment succeeds. Then Billing shows the package as Active with its next renewal date, and the payment appears under Past bills.
4. How renewals work
How your package renews depends on how it is paid, and Settings > Billing tells you which applies to your store. A package paid through a card subscription renews automatically every 30 days (or every year on yearly billing) until you cancel it; Billing then shows the subscription and "Manage payment method or cancel". Where the platform takes payments without a card subscription, nothing is charged automatically: you receive reminder emails before the renewal date and pay the upcoming bill under "Current billing cycle" with "Pay early".
- Paying early on a manual renewal moves your renewal date forward by one cycle; you never lose time already paid for.
- If a renewal is not paid, the package shows as past due and Billing shows the date until which your store keeps working; after that the storefront goes offline until you pay.
5. Cancel your package
Under "Change package" click "Cancel package". The confirmation explains that your package runs until the renewal date, the storefront then closes, you are not charged again (no refund for the rest of the cycle) and nothing is deleted for at least 90 days. Confirm with "Cancel at the end of the cycle", or keep it with "Keep my package". You can undo the cancellation from Billing before that date.
Completion checklist
- Billing shows the package you paid for as Active with a renewal date.
- The payment is listed under Past bills with Download.
- You know whether your package renews automatically through a card subscription or is renewed by hand with Pay early.
Troubleshooting
The payment window says the payment could not start, or closes without a result.
Nothing was charged and your current package, theme or app tier stays exactly as it was. Try again in a few minutes. If it keeps failing, the platform's card payment provider is not live yet for this region: contact support with your store address and what you were paying for, and the team will complete the activation with you.
I paid but Billing still shows the old package.
Reload the Billing page. If it has not changed after a few minutes, send support your store address and the payment reference from your receipt; do not pay again.
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Try, buy and publish a theme
Add a theme from the Theme Store as a draft, customise it, publish a free theme or buy a premium one when you are ready.
Illustrated guide: lulu.us.com/help/buy-and-publish-a-premium-theme
Before you startFree themes publish immediately. A premium theme is a one-time purchase in USD with lifetime use on the store that buys it; you can try and customise it free and pay only when you publish. You need the online-store permission.
1. Open Online Store and browse themes
Online Store shows your current Live theme and a "Draft themes" section. Click "Browse themes" to open the Theme Store inside your admin, or "Visit Theme Store" to open the public Theme Store site. Filter by price, industry, style or features and open a theme.
2. Click "Try theme"
The theme is added to your drafts and you return to Online Store. Trying a theme is always free, including premium themes. Until you buy a premium theme, you can customise and preview it, but you can't edit its code or publish it.
3. Customise the draft
Click "Edit theme" to open the theme editor and change sections, colours, fonts and pages. Changes save to the draft only; your live shop is untouched until you publish.
4. Publish a free theme
Click "Publish" on the draft. It becomes your Live theme and the previous theme moves to drafts so you can switch back at any time.
5. Buy a premium theme, then publish
A premium draft shows "Buy to publish" with its price in USD instead of "Publish": click it, pay in the secure payment window, and the draft is published once the payment succeeds. You can also open the theme's page in the Theme Store and click "Buy" first. It is a one-time purchase with lifetime use of the theme on this store and no renewal; each store buys its own copy.
- Updates the theme's maker publishes later reach new installations; your installed copy and its customisations are never overwritten.
Completion checklist
- The theme you want shows as Live under Online Store.
- Your storefront reflects the published draft.
- For a premium theme, the theme's page shows "Owned" and the payment is listed under Settings > Billing > Charges.
Troubleshooting
Publish says "Buy to publish" on a draft theme.
The draft is a premium theme you have not bought for this store. Click "Buy to publish" (or "Buy" on the theme's page in the Theme Store), complete the payment, then publish. You can keep customising the draft for free in the meantime.
The payment window says the payment could not start, or closes without a result.
Nothing was charged and your current package, theme or app tier stays exactly as it was. Try again in a few minutes. If it keeps failing, the platform's card payment provider is not live yet for this region: contact support with your store address and what you were paying for, and the team will complete the activation with you.
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Install apps and pay for app plans
Install an app with its consent step, choose a free plan, free trial or paid plan, pay for it each period, and cancel or uninstall cleanly.
Illustrated guide: lulu.us.com/help/pay-for-app-plans
Before you startApps come from the App Store inside your admin (Apps > Lulu App Store; while no app is installed the sidebar also shows "Add apps") or from apps.lulu.us.com. Installing always shows what the app can access before anything is added. App plans are billed in USD for each 30-day period (365 days on an annual plan) and are never charged to your card automatically. You need the apps permission.
1. Open an app's page and click "Install"
The page shows pricing, rating, developer and a plain-language summary of what the app does on your store.
2. Review the confirmation, then confirm
The confirmation lists what the app does, which data it can read or edit and what it costs. Click "Install" there to add it. The app appears under Apps in the sidebar.
3. Find your installed apps
Apps lists every installed app with its plan and status, with Open, Manage plan and Uninstall actions. Each app has its own workspace: setup checklist, activity and usage.
4. Choose a plan: free, free trial or paid
On the app's listing go to Pricing, or click "Manage plan" on Apps. "Choose plan" picks a free plan straight away or opens payment for a paid plan. "Start free trial" starts a paid plan free for the number of days shown on that plan, without a card; trial lengths vary by app, and you get a trial only the first time you choose a paid plan of that app. A free plan marked "Development stores only" is free only while your store is still in development; once it is live, choose a paid plan.
- A paid plan starts the app's normal free trial (usually 14 days), then you pay for it. This happens whether or not your store is live.
- An app labelled "Free to install" usually has a development-only free plan; budget for a paid plan when you launch.
5. Pay for the plan each period
App plans are never charged automatically. When a trial is running or a payment is due, the plan shows "Pay now" with the amount; after paying it reads "Renew now" so you can pay the next period early. Pay from the app's listing, from its workspace (Plan & billing > Manage plan) or from Settings > Billing > App subscriptions. You get reminder emails 7 days and 3 days before the due date and on the day itself.
- If a period ends unpaid, the plan shows "Past due" and the app is paused ("Suspended") 3 days after the due date until you pay. Your settings are kept.
- If an app's payment is due when you go live, the Go live page (Home > Go live) collects it before the store opens. An app still in its free trial is not charged when you go live: it bills when the trial ends. Each app then renews on its own 30-day cycle.
6. Add app blocks, cancel or uninstall
Apps that add storefront blocks appear in the theme editor's Apps panel; add their blocks to your pages from there. To stop paying, click "Cancel plan" under Pricing on the app's listing: you keep access until the end of the period you paid for, then the app is paused. To remove an app click "Uninstall"; check the listing for what happens to its data.
Completion checklist
- The app appears under Apps with the plan you expect.
- A paid plan shows its trial end date, its renewal date or "Pay now" in Plan & billing.
- Apps with "Development stores only" free plans have a paid plan chosen before you go live.
- Storefront blocks from the app are added where you want them.
Troubleshooting
My trial or period ended and the app's paid features stopped.
An unpaid plan becomes "Past due" and the app is suspended 3 days after the due date. Open the app's listing or workspace and click "Pay now", or use Settings > Billing > App subscriptions > Manage plan. Your settings are kept and the features return once the payment succeeds.
An app's free plan says "Development stores only".
That free plan is only for stores that are still in development. Your store is live, so choose one of the paid plans; if you have never trialled that app, the paid plan starts with a free trial.
The payment window says the payment could not start, or closes without a result.
Nothing was charged and your current package, theme or app tier stays exactly as it was. Try again in a few minutes. If it keeps failing, the platform's card payment provider is not live yet for this region: contact support with your store address and what you were paying for, and the team will complete the activation with you.
I cannot find this page or action.
Check the store shown at the top of the admin. On a phone, open the navigation menu first. Ask the store owner to confirm your permissions and whether the feature is available for this store.
What should I send support?
Send your store address, the page you were using, the steps you took, and the exact error text. Include a screenshot with private customer details hidden. Do not share passwords, API keys, or full payment information.
Partners: build a theme in a dev store and export it
Use the standard theme editor in a sandbox store, then download the package you submit.
Illustrated guide: lulu.us.com/help/partner-build-and-export-a-theme
Before you startYou need a dev store. There is no separate partner theme tool — you build in the same editor merchants use. Start from a free theme: a paid Theme Store theme stays a trial on a partner store, so its code is read-only and it can't be published.
1. Open the theme
In the dev store admin open Online Store. The live theme is at the top; the rest are under Draft themes. Choose Edit theme on a draft, or Customize on the live theme.
- Work on a draft while you build, so the storefront preview stays stable.
2. Build the theme
Add, reorder and configure sections and blocks in the left-hand tree, and set theme settings. Save when the preview is right.
- Custom code lives under the theme's “…” menu → Edit code: custom CSS, custom JavaScript up to 100,000 characters, and head snippets up to 20,000 characters.
- Test the storefront itself, not only the editor preview.
3. Download the theme file
Return to Online Store, open the “…” menu on the theme and choose Download theme file. You receive theme_export__<store>__<theme>__<date>.zip.
- Keep the download: a published theme package has no stored release history and no rollback.
4. Know what is inside the package
shopwise-theme.json at the root of the zip is the main file Lulu reads back. config/settings_data.json, templates/*.json, config/groups.json and assets/custom.css are copies of the same data that you can edit instead; sections/*.json, the READMEs, assets/custom.js and snippets/head-snippets.html are for reading only.
- An edited copy is used in place of the matching part of shopwise-theme.json; an untouched copy changes nothing. Change one part in one place only: if both changed, shopwise-theme.json wins. The upload lists the files it used and warns you about anything left out.
- The full file format is in “Theme package format reference”.
- A Shopify Liquid theme export is not a Lulu package and is refused on import with a message that says so.
- The import limit is 5 MB.
Completion checklist
- The theme renders correctly on the dev store's storefront.
- You have the exported zip, or you know which dev-store theme to snapshot.
Troubleshooting
Can I submit a Liquid theme from another platform?
No. Lulu imports its own export format, identified by shopwise-theme.json. A Liquid archive is rejected with a specific message rather than partly imported.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Partners: review, approval and publication
Follow a submission through review and understand what approval publishes.
Illustrated guide: lulu.us.com/help/partner-review-and-publication
Before you startReview is carried out by the Lulu team. Turnaround times vary and the portal does not show an estimate.
1. Follow the status
Open the dashboard and read the Status column under Your submissions: Draft, Submitted, In review, Approved or Rejected.
- Draft is private to you. Submitted means it is queued. In review means someone has picked it up.
2. Read the outcome
Open a submission to see the reviewer's notes with the decision and the date it was reviewed.
- A rejection always carries notes explaining what has to change.
- A submitted item is locked while it is reviewed; the detail page is read-only and there is no editor for a submission in flight.
3. Understand what approval does
Approval publishes. A theme becomes a Theme Store listing on themes.lulu.us.com; an app becomes an App Store listing on apps.lulu.us.com and in every merchant's in-admin app browser.
- Your partner account owns the published row, which is what puts it on the Listings page.
- A partner app is marked as a partner listing, so it is never presented as a built-in Lulu feature.
- There is no separate publish button for you to press.
4. Correct a rejected submission
Create a new submission with the corrections and send that one. There is no resubmit action on a rejected row.
- Keep the reviewer's notes to hand so the new submission answers each point.
5. Know what is not reviewed again
Only the initial submission is reviewed. After approval, listing edits save live, and a replacement theme package is published immediately without a second review.
- Treat every post-approval save as a release to merchants.
Completion checklist
- You can read the current status and any reviewer notes.
- You know that approval publishes automatically.
- You know that later edits are not re-reviewed.
Troubleshooting
How long does review take?
Review is done by the Lulu team and times vary. The portal shows no estimated turnaround. Contact Lulu support if a submission has been waiting unusually long.
My submission is approved but I cannot find the listing.
Open Listings in the partner portal. Themes and apps you own appear there with a View link to the public page. If it is missing, contact Lulu support with the submission title.
Why is a control missing or unavailable?
Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.
Roles and permissions for your team
Know what each of the nine built-in roles can do, build a custom store or POS role from the real permission groups, and understand who can create, assign and delete roles.
Illustrated guide: lulu.us.com/help/roles-and-permissions-for-staff
Before you startYou need the store owner account, a role with "Manage roles" to create, edit, duplicate or delete roles, or a role with "Manage users" to assign existing roles to people on the Users tab. None of the nine built-in roles can be edited or deleted — duplicate one to start a custom role with almost the same permissions.
1. Open the Roles tab
Go to Settings → Users and permissions, open Users, then open the Roles tab. Roles are split into two sections — Store roles (access to the admin) and POS roles (access to the Point of Sale register) — and the POS roles section only appears once the Point of Sale app is installed. Each row shows the role's name, description, how many people hold it, and either a "Managed by Lulu" badge or "Custom".
- The Users page has four tabs: Users, Roles, Collaborators, and Security.
2. Know the nine managed roles
Every store starts with nine managed roles. They're locked — a lock icon, disabled checkboxes — and kept up to date automatically, so duplicate one if you want something close but editable:
- Administrator (store) — access to almost every feature, including users, roles and every sensitive permission. Can't change store ownership, and can't pause, cancel or deactivate the store — those stay with the owner.
- Store user administrator (store) — invites, edits, suspends and removes people and assigns them store roles. Can't create, edit or delete roles, and opens nothing else in the admin.
- POS administrator (pos) — every Point of Sale permission, plus POS user management, device setup and POS roles.
- POS full permissions (pos) — every Point of Sale permission at the locations they're assigned to, plus POS user management. Can't create or edit roles and can't set up devices.
- POS user administrator (pos) — adds and removes POS-only users and assigns them POS roles, with basic selling (discount codes, creating and viewing customers, saved carts). No refunds, cancels, custom discounts or cash drawer access.
- POS device setup (pos) — only pairs new devices to a register. No access to the register or the rest of the admin.
- App developer (store) — builds and edits this store's custom apps under Settings → Develop apps. No access to store data and no billing.
- Staff (store) — day-to-day order work: view and manage order information, fulfill and ship, export orders, and work abandoned checkouts; view (not create or edit) draft orders, products and customers; view companies; reports, marketing and discounts; themes; and view billing. No settings, finance or user management.
- Collaborator access (store) — for partners working on your store. The default covers themes, products, orders, apps, shipping and store settings. It does not include managing users and roles, changing the plan, Point of Sale, anything financial, approving paid app charges, exporting customers, exporting orders or exporting a store backup. It's given automatically when you approve a partner's collaborator request or grant access from Onboarding partners → My requests. To change what one partner can do, open the Collaborators tab and click "Edit access" next to them; this works on every plan. A collaborator can never be given user or role management, plan changes, Point of Sale or backup restore.
3. Choose a category when you create a custom role
Select "Create role" on either section of the Roles tab. Pick Store role (admin access) or POS role (register access) — this can't be changed once the role exists. Custom store roles need a plan above the entry plan; custom POS roles need the Point of Sale app on the Retail or Pro package (the tab explains whichever gate applies, with a link to upgrade). Then enter a name (up to 80 characters) and an optional description (up to 280), and tick the permissions it should have. Two permissions you might expect to see — Merge customers and Manage and add custom pixels — are left out of the picker until those features ship, even though their permission keys already exist in the system.
- Permissions are grouped: Home, Orders, Draft orders, Products, Inventory, Catalogs, Gift cards, Customers, Analytics, Marketing, Discounts, Content, Files, Online store, Checkout and customer accounts, Companies, App development, Store settings, Finance, Apps and channels, and Point of Sale.
- Ticking a permission also selects the ones it depends on — for example, Products → Edit price selects Products → View. A POS role can only hold Point of Sale permissions.
- For a store role, you can also limit it to specific installed apps under "App permissions" — leave every box empty to allow every app.
- A store can have up to 30 custom roles in total, store and POS combined.
4. Only hand out what you hold yourself
You can only put a permission into a role, or give someone a role, that you hold yourself — and at every location where you can use the register. If you have POS full permissions at one location but only basic selling at another, you can't give someone at that second location anything beyond what you hold there (refunds included), even though you could at the first. Only the store owner or an Administrator can give a role "Manage users" or "Manage roles"; "Manage POS users" can also be given by a POS administrator or by anyone who already manages store users.
5. Assign more than one role to a person
A staff member can hold several roles at once; their effective permissions are everything those roles allow, combined. Choose roles when you add someone, or use "Change roles" on their row on the Users tab — a POS-only user is only ever offered POS roles there.
- Example: give someone both "Staff" and "POS full permissions" if they work the register and the back office.
6. Know who can manage and assign roles
Creating, assigning and deleting roles are gated separately:
- Create, edit, duplicate or delete store roles — the owner or an Administrator.
- Create, edit, duplicate or delete POS roles — the owner, an Administrator, or a POS administrator.
- Assign or unassign store roles, and invite, edit, suspend or remove store staff — the owner, an Administrator, or a Store user administrator.
- Assign or unassign POS roles, add or remove POS-only users, set POS PINs and location access — the owner, an Administrator, POS administrator, POS full permissions, or POS user administrator.
7. Duplicate or delete a custom role
"Duplicate" copies any role — managed or custom — into an editable "Copy of …" role with the same category and permissions, fitted inside your own access. "Delete role" removes a custom role. While anyone still holds it — as a role, or as a per-location POS assignment — the delete is refused with a count of how many people and locations use it; confirm again to force it through, which removes the role from every one of them in a single step. Anyone left without a role loses access to the store until you give them one, and a location that would be left with no assignment at all is never allowed to go through — reassign those people's location access first.
Completion checklist
- Every staff member holds at least one role that matches their job.
- Billing, customer-data-export and tax-document permissions are limited to people who need them.
- You removed a custom role from everyone who holds it — as a role and at every location — before deleting it.
Troubleshooting
A staff member can't see a page I expect them to have.
Check every role they hold — permissions combine across roles, and the built-in Staff role is mostly view-only outside order handling (it can't create or edit products, customers, draft orders or inventory, or change settings). Add the missing permission through a custom role, or assign Administrator if that's really what they need.
I can't edit one of the nine built-in roles.
All nine managed roles are fixed and refreshed automatically — their checkboxes are disabled and they show a "Managed by Lulu" lock. Duplicate the one you want, then edit the copy.
Creating a custom role says my plan doesn't allow it.
Custom store roles need a plan above the entry plan — that's the message you'll see until you upgrade. Existing custom roles keep working if you later downgrade; only creating a NEW one is blocked.
Creating a POS role says I need to upgrade Point of Sale.
Custom POS roles need the Point of Sale app on the Retail or Pro package. The nine managed roles — including the four POS ones — work on every package, Lite included; it's only a brand-new custom POS role that needs the upgrade.
Giving someone a role was refused, and the message names one of their locations.
That's the ceiling rule applied per location: you can only hand over permissions you hold at that SAME location. If you have POS full at one location but only basic selling — no refunds — at another, you can't give someone refund permissions at the second location even though you could at the first. The message lists exactly what's missing and where.
Deleting a role says people or locations still use it.
That's the normal check before a delete — it won't remove a role out from under anyone by accident. The dialog shows how many people hold it and how many POS location assignments use it; confirming again force-deletes it, taking it away from all of them in one step.
Force-deleting a role was refused, saying it would open a location to everyone.
The role you're deleting is the ONLY assignment at that location, so removing it would leave every POS user able to sign in there with full store-wide keys instead of none — the delete is refused rather than widening access by accident. Give those people direct location access first, then delete the role.
Invite POS-only staff
Add register-only accounts that sign in with a PIN or password at the till, use no staff seat, and never open the admin.
Illustrated guide: lulu.us.com/help/invite-pos-only-staff
Before you startThe Point of Sale app must be installed, and you need at least one POS role that can actually use the register. You need a role with "Manage users" or "Manage POS users" to send the invite — someone who only manages POS users can add POS-only staff, not store staff.
1. Open Add staff
Go to Users (Settings → Users and permissions), then select "Add staff" on the Users tab. Under "Type of user", choose "POS-only staff" instead of "Store staff".
- If your own role only manages POS users — not store users — "POS-only staff" is already chosen for you.
2. Give them a POS role that can use the register
Enter their name and email, then tick at least one POS role. A POS-only account needs a role that can actually use the register — one holding only "POS device setup" isn't enough on its own, and the invite is refused until you add a role with real register permissions (POS full permissions, POS administrator, POS user administrator, or a custom POS role with register keys).
- Roles that grant no register access are hidden from the picker once "POS-only staff" is selected, so you can't accidentally choose an unusable one.
3. Send the invite
Select "Send invite". A POS-only account uses none of your plan's staff seats and can't open the admin at all — there's no admin login, no two-step email code, and accepting the invite lands them on the register instead of the admin. They sign in directly at a paired device, by email and password or by a PIN you set for them.
4. Set their PIN and location access
Open Point of Sale → Staff & PINs to give them a PIN, and — on Retail and Pro — to choose which locations they can sign in at and an optional location role that replaces their store-wide POS permissions there.
5. Know what counts against your POS plan
Inviting a POS-only account doesn't use a staff seat, but once they're given a PIN or sign in with a password, they become a cashier account under your Point of Sale plan. Lite includes 2 cashier accounts; Retail and Pro are unlimited. Going over the cap after a downgrade pauses the extra accounts — after a 7-day grace period — rather than blocking the invite itself.
Completion checklist
- Every POS-only account holds at least one role that can use the register.
- PINs are set before you hand over a paired device.
- On Retail and Pro, location access matches where each person actually works.
Troubleshooting
The invite was refused, saying they need a role that can use the register.
A POS-only account exists only to sign in at the till, so "POS device setup" by itself isn't a usable role for one. Add POS full permissions, POS administrator, POS user administrator, or a custom POS role that holds real register keys, then send the invite again.
Can a POS-only account sign in to the admin at all?
No. Admin sign-in and the admin two-step email code both refuse a POS-only account, and accepting their invite lands them on the register instead of an admin sign-in — they only ever sign in at a paired device, with email and password or their PIN.
I invited someone as regular store staff by mistake and want them to be POS-only instead.
Re-send their invite — before they accept it — with "POS-only staff" selected. That switches their account type and re-checks the roles and seat limit for the new type.
Does a POS-only invite need the Point of Sale app on Retail or Pro?
No — POS-only accounts work on any Point of Sale package, including Lite, as long as the app is installed and they hold a usable POS role. It's only creating a brand-new CUSTOM POS role that needs Retail or Pro; the managed POS roles work on every package.
Require two-step verification for your team
Make everyone who signs in to your store confirm an emailed code on every sign-in, not just on new devices.
Illustrated guide: lulu.us.com/help/require-two-step-for-your-team
Before you startYou need the store owner account, or a role that includes the "Manage users" permission (Administrators and Store user administrators have it). This is a store-wide requirement on top of the standard sign-in check described in Security: account details and logged-in devices.
1. Open the Security tab
Go to Settings → Users and permissions → Users (or open Users directly), then open the Security tab.
2. Turn on "Require two-step authentication for all staff"
Switch the toggle on. It saves the moment you change it — there's no separate Save button, and it switches back if the change can't be saved. When you turn it on, every other staff member (and your own other devices) is signed out, so everyone has to sign in again with a code.
3. Know how the code itself works
There's nothing to set up per person: Lulu emails a 6-digit code to the person's own account email. Without the requirement, the code is only asked for on a device that isn't recognised, or after about 90 days without signing in; a verified device is otherwise remembered for 180 days. With the requirement on, the code is asked for on every sign-in, recognised device or not.
- There's no authenticator-app option — the code always goes by email.
4. Turning it off
Switching the requirement off returns the store to the standard rule: a code only on a new device or after long inactivity. There is no separate per-person two-step setting to turn on or off.
5. Collaborator access is on the same tab
If a partner needs access instead of a regular staff seat, use "Manage collaborators" on this same Security tab rather than inviting them as staff.
Completion checklist
- You know whether a code is required on every sign-in for this store.
- Staff know the code goes to their own account email, not a shared inbox.
- You expected everyone else to be signed out when you turned the requirement on.
Troubleshooting
A staff member says they never receive the code.
The code goes to the email address on THEIR OWN account, not the store's contact address — have them check Account → General for the address on file, and check spam.
I turned the requirement off — did that remove it from people who already set it up?
No one is removed from anything — sign-ins simply go back to the standard rule, where a code is only needed on an unrecognised device or after about 90 days of inactivity.
The toggle is disabled for me.
Only the store owner and users whose role includes "Manage users" (Administrators and Store user administrators have it) can change this. Check your role on the Roles tab.
Transfer store ownership
Hand full control of your store to an existing staff member instantly, or invite someone new by email.
Illustrated guide: lulu.us.com/help/transfer-store-ownership
Before you startOnly the current store owner can start a transfer, and you'll need to confirm your password. Collaborators aren't offered as transfer targets. This is a single-store action — it's different from a partner's "Transfer to client" hand-over of a client transfer store, whose invitation stays open for 30 days.
1. Open "Transfer ownership"
Go to Settings → Users (the Users tab). As the owner, you'll see a "Transfer ownership" button in the page header.
2. Choose who to transfer to
Pick "An existing staff member" to transfer instantly, or "Someone else, by email" to send an invitation. Only active staff who aren't collaborators are offered for an instant transfer; the email option is for someone who isn't on your staff list yet.
- An email invitation expires in 7 days, and only one invitation can be pending at a time.
3. Confirm your password
Enter your current password in the confirmation field, then select Transfer ownership (for an existing staff member) or Send invitation (for an email transfer).
4. Know what happens next
An instant transfer takes effect immediately: the staff member becomes the owner, your account becomes an administrator, and you both get a confirmation email — "This can't be undone by you afterwards." An email transfer instead shows a banner on the Users tab — "Ownership transfer pending — an invitation went to <email> (expires <date>). Nothing changes until they accept" — with a Cancel transfer button.
5. After the transfer
The new owner has full control of the store — staff, billing and settings. Your own account isn't removed; it becomes an administrator, which keeps everything except the owner-only actions such as transferring ownership.
Completion checklist
- You picked the right person — an instant transfer to an existing staff member cannot be undone by you.
- A pending email transfer is cancelled from the Users tab if you change your mind before it's accepted.
Troubleshooting
I don't see "Transfer ownership" anywhere.
Only the current store owner sees this button — not even an Administrator does. Confirm who the store owner is on the Users tab.
No one appears under "An existing staff member."
Only active staff who aren't collaborators are offered for an instant transfer. Add the person as staff first, or use "Someone else, by email" instead.
Can I transfer ownership to a collaborator?
Collaborators aren't offered as transfer targets. If you want a partner to own the store, add them as a regular staff member (or use the email option with an address that isn't already on your staff list).
Can I cancel an email invitation after sending it?
Yes — the pending-transfer banner on the Users tab has its own "Cancel transfer" button, available any time before the invited person accepts.
Manage collaborator access for partners
Share a request code with a partner, approve or deny what they ask for, choose what they can do, and remove their access when the work is done.
Illustrated guide: lulu.us.com/help/manage-collaborator-access
Before you startYou need the store owner account, or a role that includes the "Manage users" permission (Administrators and Store user administrators have it). This covers the merchant side of collaborator access — a partner's own side (requesting access with the code) is covered in the partner help center.
1. Open the Collaborators tab
Go to Users (from Settings → Users and permissions), then open the Collaborators tab. The "Collaborator request code" card shows your current code.
2. Share the code deliberately
Hand the code only to the partner or agency you actually want working on your store. Anyone who has the code can send a request, but you still approve every one individually before they get in.
3. Approve or deny each request
Under "Requests," each pending item shows the partner's name, email and an optional message. Select Approve to let them in, or Deny to turn them away.
- Approving gives the partner default collaborator access. It does not include exporting customers, exporting orders, exporting a store backup, finance or approving paid app charges.
- A collaborator never uses one of your staff seats and never receives billing emails.
4. Choose what each collaborator can do
On the Collaborators tab, under "Collaborator access", click "Edit access" next to the partner. Tick or untick sections and click "Save access". "Reset to default" goes back to the default set. This works on every plan.
- To allow exports, tick "Export" under Customers or Orders, or "Export a store backup" under Store settings.
- Collaborators can never manage users or roles, change your plan, transfer or close the store, use Point of Sale or restore a backup.
5. Regenerate the code if it's been over-shared
Select "Generate new code." The old code stops working the moment the new one is created — partners who already have active access are unaffected and keep it.
6. Remove access when the work is finished
On the Collaborators tab, find the partner under "Collaborator accounts", open the row's menu and choose "Remove collaborator" (or click "Remove access" on their request in Onboarding partners → My requests). They lose access to your admin immediately; their past activity stays in your store's history, and they'd need to send a brand-new request — or be granted access again — to come back. Access does not end when a partner order completes or a request is closed, so remove it yourself when the work is finished. Access that is not used for 90 days is removed automatically: the partner is warned by email after 75 days, and you are emailed when it expires.
7. See what a collaborator changed
As the store owner, open Settings → Activity. It lists the changes each collaborator made in your admin, with the date and time. Entries can't be edited or deleted.
Completion checklist
- The request code hasn't been shared outside the people you want to grant access to.
- Access is removed as soon as a partner's engagement ends.
- Each collaborator has only the permissions the current job needs.
Troubleshooting
A partner says the code doesn't work.
A regenerated code replaces the old one instantly, so share the CURRENT code shown on the Collaborators tab, not one from an earlier email or message.
Does approving a collaborator use one of my staff seats?
No — collaborators never consume a staff seat and never receive billing emails.
I removed someone's access by mistake.
There's no undo. They need to send a new request with your current code, and you approve it again.
I can't find the Collaborators tab.
You need a role that includes "Manage users" (Administrator and Store user administrator have it by default). Check your own role on the Roles tab.
I got an email "Collaborator requests are paused".
Someone entered the wrong request code for your store 5 times. New requests are paused for 60 minutes. Nobody got access. If you did not share your code, select "Generate new code".
A partner's access expired.
They did not sign in to your store for 90 days. Give the access back from the Collaborators tab if they still work for you.
A partner can no longer export customers or orders.
Exports are off by default since 20 November 2026. Turn them on for that partner with "Edit access".
Get email alerts for new orders
Choose which inboxes get emailed when a new online order or draft order comes in.
Illustrated guide: lulu.us.com/help/staff-order-alert-emails
Before you startThis is separate from the customer-facing order-confirmation emails covered in Notifications: review customer emails — it's what YOUR team receives, not what shoppers receive. You need a role that includes "Manage settings."
1. Open Settings → Notifications
Go to Settings → Notifications and scroll past "Customer notifications" to the "Staff notifications" card.
- "Customer notifications" above it is the template editor for shopper-facing emails — a different feature from this card.
2. Turn on the alerts you want
Check "New order" to be emailed whenever an order is placed through your online store checkout (on by default), and "New draft order" to be emailed when a draft order is created (off by default).
3. Add extra recipients
Enter a comma-separated list of up to 50 email addresses under "Additional recipients." Leave it blank and the alerts go to the store owner's email. Once you enter addresses, the alerts go to exactly those addresses — add the owner's email to the list too if they should keep receiving them.
- The same recipient list is also used for other staff alerts, such as customer return requests.
4. Save
Select Save at the bottom of the card. The setting applies to orders and draft orders from then on.
5. Remember what this does and doesn't cover
These are plain internal emails saying a new order exists — they don't replace or change the customer's own order-confirmation email, which is a separate template you edit under "Customer notifications" on the same page.
Completion checklist
- You know exactly who currently gets a new-order email for this store.
- If you added recipients, the owner's address is on the list too (if they still want the alerts).
Troubleshooting
Nobody received an email for a new order.
Confirm "New order" is turned on and check the recipient addresses for typos and spam filtering. Note that the alert is sent for orders placed at your online checkout; it is separate from the customer's own confirmation email.
Can I notify one specific staff member instead of the owner?
Yes — enter their email under Additional recipients. When the list has addresses, only those addresses are notified; the owner is only notified by default when the list is blank.
I want this to be a per-person preference, not store-wide.
That's not available today. Staff notifications is one on/off pair plus one shared recipient list for the whole store, not an individual opt-in or opt-out.
Understand your Analytics dashboard
Read the KPI cards, charts, conversion funnel, and breakdown tables on your Analytics home page, and know where the numbers come from.
Illustrated guide: lulu.us.com/help/understand-the-analytics-dashboard
Before you startGo to Analytics in the admin sidebar. The dashboard loads automatically for the selected date range (default: last 30 days) and refreshes each time you change the range.
1. Pick a date range
Use the date picker at the top right of Analytics to choose Today, Last 7 days, Last 30 days, Last 90 days, Last 12 months, or Custom range (pick From and To dates, then click Apply). Every number on the page recalculates for that range: the KPIs, charts, funnel and breakdown tables. The charts also show the previous period of the same length for comparison. Cancelled orders aren't counted.
2. Read the KPI row
Six cards summarise the period: Gross sales, Net sales, Orders, Avg. order value, Conversion rate and Returning customers. Each card compares the period with the previous one of the same length, for example "↑ 12.4% vs previous period", "No change", "No data", or a New badge when the previous period had nothing.
- Gross sales and Net sales are shown in your store's currency
- Conversion rate shows "—" when there's no session data to calculate it from
- Returning customers is the share of orders placed by returning customers
3. Read the Sales over time and Orders over time charts
Both charts show the current period against the previous period. Points are grouped by day for ranges up to 90 days, by week for longer ranges up to a year, and by month beyond that. If there were no sales in the range, the Sales over time chart shows "No sales data in this range."
4. Read the Conversion funnel
The funnel shows four stages for the selected range: Sessions, Added to cart, Reached checkout and Converted. Each stage has a count and the percentage drop from the stage before. Sessions are recorded automatically when shoppers view your online store. If Sessions is 0, nobody has visited your storefront in that range (for example, while it's still password-protected).
5. Review the Breakdowns section
Below the funnel, five tables break the period down by: Top products (toggle Revenue/Units), Top collections, Sales by channel (grouped by the channel recorded on each order, e.g. Online store, POS), Top discounts (by code, uses, and amount discounted), and New vs returning customers (as a two-bar split). Each table has its own "Export CSV" button.
6. Find deeper reports
The "See all reports in the Reports library" link at the bottom of the dashboard opens Analytics > Reports, the full list of reports.
Completion checklist
- Chose the date range you want to review
- Checked the KPI deltas against the previous period
- Reviewed the conversion funnel for drop-off points
- Opened the breakdown table you need and exported it if required
Troubleshooting
Why does Conversion rate show "—"?
Conversion rate needs session (visit) data to calculate from. Sessions are recorded automatically on your storefront pages, so "—" means there were no storefront visits in the selected range. This can happen with a new or password-protected store, for example.
Why does a breakdown table say "No data in this range"?
Each table only reflects orders, discounts, or sessions that actually happened inside the selected date range. Widen the range (e.g. to Last 90 days) to see more history.
What does "Refreshed" next to the page title mean?
It's the time the dashboard data was last loaded from the server. Changing the date range or reloading the page refreshes it.
Does Sales by channel include every sales channel my store sells through?
It groups revenue by the sales channel recorded on each order, for example Online store or POS. Orders with no channel are counted as Online store. It isn't a marketing attribution report.
Monitor your store in real time with Live View
Watch visitors, sessions, sales, and checkout behaviour update every 10 seconds on the Live View page.
Illustrated guide: lulu.us.com/help/monitor-your-store-with-live-view
Before you startGo to Analytics > Live View in the admin sidebar.
1. Open Live View
From Analytics, click Live View in the sub-navigation, or go directly to Analytics > Live View. The page polls the server every 10 seconds and shows "Updated Ns ago" next to the Live pill.
2. Read the top KPI row
Four live cards show: Visitors right now (distinct sessions active in the last 5 minutes), Sessions today, Total sales today, and Orders today.
3. Check Sessions by location
A bar list shows today's sessions grouped by visitor country, based on the visitor's network location, with the busiest country at the top. Visits whose country can't be identified are grouped as Unknown.
4. Check Customer behaviour
This card shows, for the last 15 minutes only: Active carts, Checking out, and Purchased — a quick read on whether current traffic is converting.
Completion checklist
- Confirmed Visitors right now matches what you expect during a launch or promotion
- Watched Checking out vs Purchased during a live sale to spot checkout drop-off
Troubleshooting
Why does Live View show 0 visitors even though I know people are browsing?
"Visitors right now" only counts storefront sessions recorded in the last 5 minutes. Visits are recorded automatically on your online store pages, but not on previews inside the theme editor or on your admin pages. Shoppers who block scripts may not be counted either.
How often does the page update?
Live View polls automatically every 10 seconds; you don't need to refresh the page. The "Updated Ns ago" label shows how fresh the data is.
Does Live View show which country a specific visitor is from?
No — Sessions by location only shows a country-level total for today, not individual visitor details.
Explore the Reports library
Browse, search, pin, and open the named reports in Analytics > Reports, and know which ones currently show live data.
Illustrated guide: lulu.us.com/help/explore-the-reports-library
Before you startGo to Analytics > Reports in the admin sidebar.
1. Browse or filter the catalog
The Reports page lists every report by Name, Category, Last viewed and Created by. To narrow the list, use the category dropdown or the Search reports box.
2. Pin reports you use often
Click the star icon next to a report to pin it — pinned reports float to the top of the list. Pins and last-viewed timestamps are saved in your browser only (not shared with other staff).
3. Open a report with live data
35 reports open the generic report page with real data today, each with a date range selector (Today, Last 7 days, Last 30 days or Last 90 days), a chart where it makes sense, a results table, and its own Export CSV button:
- Sales: Sales over time, Sales by product, Sales by product variant, Sales by vendor, Sales by product type, Sales by channel, Sales by location, Sales by customer, Discounts usage
- Acquisition: Sessions over time, Sessions by location, Sessions by referrer, Sessions by landing page
- Behaviour: Conversion rate over time, Online store conversion over time, Abandoned checkouts over time
- Customers: Customers over time, New vs returning customers, RFM customer analysis
- Finance: Finance summary, Taxes, Payments by method, Gift cards issued and redeemed
- Inventory: Inventory on hand and value, Sell-through rate by product, ABC analysis by product
- Marketing: Sessions attributed to marketing
- Profit: Gross profit over time, Profit by product, Profit by variant (see read-the-profit-reports)
- Order: Orders over time, Average order value over time, Fulfillment and delivery times
- Retail sales: Retail sales by staff
- Fraud: Fraud analysis
4. Open Landed costs by destination
Landed costs by destination (category Inventory) is the 36th live report. It opens a dedicated page instead of the generic report viewer, with its own Export CSV button — see "Track landed costs and margins" for how to read it.
5. Know the two reports that aren't built yet
Month-end inventory value and Sales attributed to marketing each open a "Not available yet" page with the specific reason: stock isn't snapshotted at month end, and orders aren't linked to the visit or campaign that brought the shopper. Unlike an empty live report, more orders won't fill these in — they need a data source your store does not record yet.
Completion checklist
- Found the report you need by name or category
- Pinned the reports you check regularly
- Checked whether the report you opened is one of the 36 that show live data, or one of the 2 that aren't built yet
Troubleshooting
I clicked "New exploration" — where's the report builder?
Lulu doesn't have a custom report builder yet; clicking New exploration shows a "Report explorations are coming soon" message.
Why does a report open but show "No data for the selected period"?
That report is one of the live reports but your store has no matching activity (orders, sessions, discounts, etc.) in the date range you picked, or — for a money report — every matching order was in a foreign currency with no saved exchange rate (see the note under the table). Try a longer range, or check the note.
Are my pinned reports visible to other staff accounts?
No — pins and last-viewed timestamps are stored in your own browser's local storage, not shared across staff or devices.
Track landed costs and margins by destination
Set up landed cost profiles for the countries you ship to, then read the Landed costs by destination report to see estimated and actual margins.
Illustrated guide: lulu.us.com/help/track-landed-costs-and-margins
Before you startYou create landed cost profiles under Products > Landed costs. The report is under Analytics > Reports > Landed costs by destination.
1. Add a landed cost profile per destination
Go to Products > Landed costs and click Add profile. Choose the destination Country, give the profile a name (for example "Standard"), and tick Active. You can only have one profile per country.
2. Add cost components
Under Components, click Add component for each cost you pay on top of the product cost: Freight, Duty, VAT, Insurance, Clearance, Handling or Other. For each one, choose a Mode: Percent (%) of the running total, Per unit, Per kg or Flat. Then enter the value, and add a label if you like. Components apply in the order listed, and you can reorder them with the up and down arrows. A percent component applies to the running total so far.
- Standard sequence recommended: freight → duty → VAT
- Use the sample-cost calculator at the bottom of the modal to preview the estimated landed cost for a test amount before saving
3. Save the profile
Click Add profile (or Save when editing). You can edit or delete a profile at any time from the Landed costs list; deleting removes it immediately.
4. Open the Landed costs by destination report
Go to Analytics > Reports and open Landed costs by destination. Choose a country, or leave it on All countries. The table shows Product, Variant, SKU, Unit cost, Country, Est. landed, Act. landed, Price, Est. margin, Est. margin % and Act. margin %.
5. Understand estimated vs actual landed cost
Est. landed is your profile's components applied to the product's unit cost. Act. landed comes from purchase orders you've marked as received that have extra costs recorded on them (such as freight or duty). It's a weighted average per variant. Until a variant has that data, it shows "—".
6. Export or page through results
Click Export CSV (top-right) to download the current filter's data. Results page 50 rows at a time with Previous/Next controls.
Completion checklist
- Created a landed cost profile for each country you ship to
- Added freight/duty/VAT components in the right order
- Reviewed estimated margins by destination
- Checked which products are missing a weight (needed for per-kg components)
Troubleshooting
Why is Est. landed blank for some rows?
Either no active landed cost profile exists for that product's destination country, or a per-kg component can't be calculated because the variant has no weight set — add a weight on the product's Shipping details.
Why is Act. landed always "—"?
Actual landed cost comes from received purchase orders that have costs (freight, duty and so on) recorded. It stays "—" until you've received a purchase order for that variant with those costs added.
Can I apply one profile to multiple countries?
No. Each profile covers exactly one destination country, and you can only have one profile per country. Create a separate profile for each country, even if the components are the same.
Does Lulu remit the duties/VAT this report estimates?
No. Landed cost profiles are for your own margin estimation only — Lulu doesn't collect, remit, or file duties or import taxes on your behalf.
Export analytics data to CSV
Download any report in the library, the dashboard's breakdown tables, and the Landed costs report as CSV files for spreadsheets or accounting.
Illustrated guide: lulu.us.com/help/export-analytics-data-to-csv
Before you startEvery live report page under Analytics > Reports has its own Export CSV button, and so do the Analytics dashboard's breakdown tables.
1. Set the date range first
A report page's Export CSV button uses whatever date range its own selector is showing — Today, Last 7 days, Last 30 days or Last 90 days. The Analytics dashboard's own exports use the dashboard's separate date picker (Today, Last 7/30/90 days, Last 12 months, or a custom range). Days are counted in your store's configured time zone (Settings > General), not UTC. Cancelled orders are left out of every export.
- Today
- Last 7 days
- Last 30 days
- Last 90 days
2. Export a report from the library
Open any of the 33 reports under Analytics > Reports and click Export CSV at the top of the page. It downloads the same rows the table on screen is showing, for the date range you've selected — not capped at 10 rows the way the dashboard's breakdown cards are.
3. Export a dashboard breakdown table
On Analytics, each breakdown card (Top products, Top collections, Sales by channel, Top discounts, New vs returning customers) has an Export CSV button. It downloads that table for the dashboard's current date range, up to the 10 rows shown on screen. Money columns come as a whole-cents value plus a decimal value: for example, Revenue (cents) and Revenue ($). The decimal column holds the amount in your store's currency, even though its heading shows $.
4. Export the Landed costs report
On Analytics > Reports > Landed costs by destination, click Export CSV at the top right. It downloads the data for the country you've selected, or all countries if you haven't picked one.
5. Know what's left out of a money report
An order placed in another currency without a saved exchange rate is left out of a money report rather than added at face value — the page tells you under the table how many orders were excluded and why. A report that doesn't read order money (for example a sessions report) never shows this note.
6. Open the file
Downloaded CSVs open directly in Excel, Google Sheets, or Numbers. Money values export as plain numbers (not pre-formatted currency) so they can be used directly in spreadsheet formulas.
Completion checklist
- Set the date range (or country filter, for Landed costs) you want before exporting
- Downloaded the CSV and confirmed the row count matches what you expected
- Checked the excluded-orders note on a money report before trusting its total
Troubleshooting
Can I export the full Reports catalog, or just the dashboard breakdowns?
Both. Every report under Analytics > Reports that shows live data — all 33 on the generic report page, plus Landed costs by destination — has its own Export CSV button today, as well as the dashboard's breakdown tables.
Can I schedule a CSV to be emailed to me automatically?
No — every export in Lulu is an on-demand download; there's no scheduled or emailed export.
Why does my exported file only have 10 rows?
That's only true of the Analytics dashboard's breakdown cards, which are capped at the 10 rows shown on screen. A report opened under Analytics > Reports exports every row for the date range you picked, not just what's visible. The Landed costs export isn't row-limited either.
A report's export seems to be missing some orders.
Check the note under the table — an order placed in a currency the store has no saved exchange rate for is left out of money reports rather than guessed at. It's counted in the note, not silently dropped.
Connect Google Analytics and ad pixels
Link a GA4 property to your storefront and add Meta or TikTok pixel IDs from the Analytics dashboard.
Illustrated guide: lulu.us.com/help/connect-google-analytics-and-ad-pixels
Before you startGo to Analytics in the admin sidebar and scroll down to the Google Analytics & ad pixels card, just above the link to the Reports library. You need a GA4 property. Meta and TikTok pixels are optional.
1. Add your GA4 Measurement ID
In GA4, go to Admin > Data streams > your web stream and copy the Measurement ID (it starts with G-). Paste it into the Measurement ID field and click Save. The Google tag is added to your storefront and tracking starts straight away. The card's badge changes from Not linked to Tracking active. This works on its own, whatever you do in the steps below.
2. Add your GA4 Property ID
In GA4, go to Admin > Property details and copy the numeric Property ID. Paste it into the Property ID field and click Save. This is what lets Lulu pull report data back into your dashboard (separate from tracking).
3. Add Meta and/or TikTok pixel IDs (optional)
Enter a Meta pixel ID (from Meta Events Manager > Data sources) and/or a TikTok pixel ID (from TikTok Ads Manager > Assets > Events > Web events) in the same form, then Save. These send page-view and shopping events to those ad platforms from your storefront.
4. Grant Lulu's service account Viewer access (required to see GA reports in the dashboard)
After you save a Property ID, the card tells you what's still needed. If it says Lulu's Google service account isn't configured on this platform yet, GA reports can't be shown inside Lulu at the moment. You can't fix this from your side, and your storefront tracking still works. If the card shows a service-account email instead, go to GA4 > Admin > Property access management and give that exact email Viewer access to your property.
5. Check the GA report panel
Once access is granted, the card shows Active users, Sessions, and Page views for the last 28 days, a sessions-over-time chart, and a Top pages table — all pulled live from your GA4 property.
Completion checklist
- Pasted the GA4 Measurement ID and confirmed tracking shows "Tracking active"
- Pasted the GA4 Property ID
- Granted the Lulu service account Viewer access on the GA4 property
- Added Meta/TikTok pixel IDs if you run ads on those platforms
Troubleshooting
The card says "Reports are almost ready: Lulu's Google service account isn't configured on this platform yet." What do I do?
It means the Google service account that reads GA4 reports hasn't been set up for Lulu yet. This is a platform-wide setting, so you can't fix it from the Property ID field. Storefront tracking with your Measurement ID still works. Contact support if you'd like to know when GA reports will appear in the dashboard.
I granted access but it still won't pull data in — why?
Double-check you granted Viewer access to the exact service-account email shown in the card, on the same GA4 property whose numeric Property ID you entered. The card also surfaces Google's own error message when the connection fails.
Does adding a pixel ID require any code changes to my theme?
No — once saved, Lulu injects the Google tag, Meta pixel, and/or TikTok pixel into your storefront automatically.
Is my GA4 connection OAuth-based, like connecting a Google account?
No — there's no OAuth sign-in step. You paste your Property ID and separately grant Lulu's platform-level service account Viewer access inside your own GA4 property settings.
Read the profit reports: gross profit and margin
Record a cost per item, then read Gross profit over time, Profit by product and Profit by variant to see what each sale actually earned.
Illustrated guide: lulu.us.com/help/read-the-profit-reports
Before you startYou need permission to view reports (and, to see or edit costs, the View cost / Edit cost permissions). Profit is only as good as the costs you enter, so start by filling in Cost per item on your products.
1. Record a cost per item
Open Products, choose a product, and in the Pricing card select the Cost per item chip and enter what one unit costs you (for a product with variants, open the variant and fill in Cost per item in its Pricing card). Customers never see it. The Pricing card shows Profit and Margin as you type.
- You can also fill the Cost per item column for many products at once in the bulk editor.
- Entering a cost only affects sales made from then on — see the next step.
2. Know that the cost is saved on each sale
When an order line is created, your store copies that variant's cost per item onto the line. Changing the cost later never rewrites past orders, so a price rise from your supplier does not distort last month's margin.
- Saved for: online checkout, point-of-sale sales, draft orders you complete, marketplace seller orders, subscription renewals, items you add when editing an order, external POS sales, imported channel orders (matched by SKU) and dropship orders.
- Not saved (always "cost unknown"): tips, POS service-charge lines, custom lines that match no variant, and every order placed before costs started being saved on orders.
3. Open a profit report
Go to Analytics > Reports. Use the category dropdown (set it to Profit) or Search reports, then open Gross profit over time, Profit by product or Profit by variant.
- Gross profit over time: one row per day, in your store's time zone.
- Profit by product: one row per product, up to 250 rows.
- Profit by variant: one row per variant, with its variant name and SKU.
4. Choose a period
Use the range selector at the top right: Today, Last 7 days, Last 30 days or Last 90 days. Every report in the library uses these same four ranges; there is no custom date range or compare-to-previous-period yet.
5. Read the columns
Each report shows Net units, Net sales, Cost of goods, Gross profit, Margin and Items without a cost (plus Day, Product or Variant as the first column). Gross profit is net sales minus cost of goods, and Margin is gross profit as a percentage of net sales.
- Net sales are line totals after line discounts, minus refunded units, so a discounted, partly refunded line never goes negative.
- Cancelled orders, gift-card sales and tips are left out. POS service charges are not merchandise and are left out too.
- Order-level discounts, shipping and fees are not deducted, so this is gross profit on goods, not net profit.
6. Deal with Items without a cost
The last column counts units sold that have no saved cost. Those units are left out of Cost of goods, Gross profit and Margin (they are never priced from today's cost), so a high number means the margin on that row is based on only part of the sales. Fill in Cost per item for the affected products; new sales will then be counted. Older orders cannot be filled in afterwards.
7. Check the note under the table
If any orders were placed in a foreign currency without a saved exchange rate, they are left out of every money report and a note says how many ("N orders were left out…"). Orders in another market currency that do have a rate are converted to your store currency using the rate saved on the order.
8. Export to CSV
Select Export CSV at the top right to download the same table for the selected period. Money is in major units with the currency in the column header, and margin is a percentage from 0 to 100.
Completion checklist
- Cost per item is filled in for the products you sell most.
- You know that a cost is saved on the order line when it is sold and never changes afterwards.
- You check Items without a cost before trusting a margin.
- You remember order-level discounts, shipping and fees are not deducted.
Troubleshooting
Margin is blank or Gross profit is 0 for a product.
None of that product's sold units had a saved cost, or no units sold in the period. Check the Items without a cost column, add Cost per item to the variants and sell again.
I changed a cost but last month's profit did not change.
That is intended. The cost is copied onto each order line when it is sold, so history keeps the cost you had at the time.
Why is Gross profit lower than my Finance summary?
The profit reports use net sales of items with a known cost and subtract that cost; they ignore shipping, tax, tips and order-level discounts. Use the Finance summary report for those.
A sale I made at the register is missing from Profit by product.
POS service-charge lines and custom lines with no matching variant have no cost and no product, so they are left out. Cancelled orders are also excluded.
Develop a custom app: API access tokens, scopes, and webhooks
Create a custom app for your own integration (a WMS, ERP, or other system), choose exactly the data it can read or write, and subscribe it to webhooks.
Illustrated guide: lulu.us.com/help/develop-apps-api-tokens-webhooks
Before you startYou need store owner access, or staff with the "Manage and install apps" permission.
1. Open Develop apps
Go to Settings → Apps and sales channels → Develop apps.
2. Create an app
Click Create an app, enter an App name (for example "Warehouse sync"), and tick the Scopes it needs. Scopes are grouped by resource (products, orders, customers, inventory, fulfillments, discounts, locations and more), each with a Read and Write option; Read products and Read orders are ticked to start with. Click Create app.
3. Install it to get a token
The new app appears as a card. Click Install (new token) on it to get an Admin API access token. The token is shown once, in the "Copy your Admin API access token now" card, so copy it straight into your integration's configuration.
4. Scope it tightly
Grant only the scopes the integration needs, for example Read products and Read orders for a reporting tool, adding Write inventory only if it must change stock. Read orders covers the last 60 days; tick Read all orders only if the integration needs older orders. Scopes can't be changed after the app is created, so create a new app if you need different ones.
5. Use the dedicated POS preset if that's the goal
To connect your own in-store POS software, use the Connect a POS system card at the top of the page instead. It creates an app with the right access for a POS and shows its token straight away (see guide-connect-local-pos).
6. Review and revoke tokens
Each app's card lists its tokens with their Scopes, Last used date and Status. Click Revoke on a token that may be compromised or is no longer used, and Install (new token) for a fresh one. Uninstall stops every token of the app immediately.
7. Subscribe to webhooks
Go to Settings → Notifications and, in the Webhooks section, add a webhook so Lulu sends event payloads (for example orders/create, products/update or inventory_levels/update) to your integration's https:// endpoint instead of it polling the API. See "Staff order alerts and webhooks" for the full flow.
Troubleshooting
I lost the access token.
It can't be shown again. Click Install (new token) on the app's card for a new one, then Revoke the old token.
My integration gets 403 errors on some calls.
The token doesn't have the scope that call needs. Compare the app's scopes (shown on its card) with the call. Because scopes can't be edited, create a new app with the extra scope and install it for a new token.
I can't see the Create an app button.
Developing apps is available to the store owner and to staff with the "Manage and install apps" permission.
Understand an app's install consent: permissions and data access
Before an app is installed, review exactly what it can see and edit, any setup requirements, and its price — so you know what you're agreeing to.
Illustrated guide: lulu.us.com/help/app-install-consent-permissions
Before you startYou need the store owner account or a staff account allowed to install apps.
1. Open the app's listing
In your admin, open the App Store, open the app you're considering, and click Install. This only opens a confirmation window; nothing is installed yet.
2. Read the consent modal
A window titled "Install <App name>" opens. At the top it says what kind of app it is, for example Built-in feature, Built by Lulu, or Third-party app, with a one-line explanation.
3. Review data access
Under "This app will be able to:", check the View lines (data it can read) and the Edit lines (data it can change). An app that touches no store data says "This app doesn't request access to your store data."
4. Review requirements
If the app has requirements, they're listed under Requirements with a status icon: a tick when met, a warning when not met, and a dashed circle for a step you complete after installing (for example "Enable in the theme editor"). An app that can't work yet (for example one that needs an outside account that isn't available) can't be installed at all: its Install button is disabled and the listing says "Not available yet" and why.
5. Check the price line
Under What it costs, the window states whether the app is free, has a free plan with paid upgrades, is free only while your store is in development, or starts a free trial and what it costs afterwards.
6. Confirm or cancel
Click Install in the window to add the app, or Cancel to back out without installing anything. Installing a paid app starts its free trial if it has one; the confirmation message tells you when the trial ends.
Troubleshooting
An app is asking for more access than I expected.
Cancel the install and read the View/Edit lists again — if an app wants write access to Orders, for example, ask the developer why before installing, or choose a narrower alternative.
Does installing charge me immediately?
No. Installing a free app costs nothing, and installing a paid app starts its free trial when it has one. If an app's free plan is for development stores only and your store is live, the app installs but stays switched off until you pay for a plan.
How app and theme charges appear on your monthly bill
On the monthly bill, Lulu combines your plan, app plans, fees and POS charges into one payment every 30 days. Here's how app charges land on it.
Illustrated guide: lulu.us.com/help/app-charges-monthly-bill
Before you startThis applies to stores on the monthly bill: Settings → Billing then shows a Billing card with "Your next bill". Stores not yet on the monthly bill pay each app plan from the app's listing (see pay-for-app-plans).
1. Know the model
Your plan, app charges and fees are combined into one bill every 30 days and charged to your card on file on the bill date, rather than a separate charge per app on its own schedule.
2. See what's coming due
Go to Settings → Billing. The Billing card shows "Your next bill" with its date and an estimated total, and the Monthly bill card breaks down the current cycle's estimate.
3. Buy an app mid-cycle
When you start a paid app plan partway through your cycle, the app's own 30-day period starts that day, and that full period is added to your next bill. There is no partial-day charge. Upgrading an app plan adds the price difference for the rest of the period to your next bill; a downgrade takes effect at the end of the app's period.
4. Check yearly app plans separately
A yearly app plan is added to a bill as one line covering 365 days and doesn't appear again until its next year.
5. Review past bills
In the Monthly bill card, each past bill has a Receipt button (a printable receipt or bill) and a CSV button to download its lines.
6. Handle a failed charge
If a bill's charge fails, Settings → Billing shows the problem with a Pay now (or Confirm payment) button, and you'll get reminder emails. If the bill stays unpaid past the grace period, the store is frozen: shoppers see a temporarily-unavailable page, the admin opens on Settings → Billing, and the POS and API are paused. Nothing is deleted, and paying reopens the store.
Troubleshooting
I installed an app on day 20 of my cycle. Why does my next bill show the full app price?
The app's 30-day period started on the day you installed it, so your next bill carries that whole period. It is not charged again until that period ends.
An app charge isn't on my monthly bill.
Check whether your store is on the monthly bill (Settings → Billing shows "Your next bill"). If it isn't, app plans are paid from the app's own listing with Pay now. A yearly app plan only appears on the bill once a year.
Understand a customer's profile page
Read the KPI tiles, order history, and side cards on a single customer's record.
Illustrated guide: lulu.us.com/help/understand-a-customer-profile
Before you startOpen a customer from Customers, or from the customer link on one of their orders.
1. Open the profile
Go to Customers and click a customer row. The Prev/Next arrows in the page header move to the next newer or older customer without going back to the list.
2. Read the four KPI tiles
Amount spent, Orders, Customer since, and RFM group sit across the top. RFM group (Prospects, Promising, Loyal, Champions, or At risk) is worked out from how recently the customer ordered, how often, and how much they spent compared with your other customers. A customer with no orders that weren't cancelled shows Prospects.
3. Check “Last order placed”
Shows the order name, date, total, and payment/fulfillment badges, with View order and Create order (a draft prefilled to this customer) buttons. If they haven't ordered yet, it's an empty state with just Create order.
4. Scroll the Orders table
Every order this customer has placed, in one list. Click a row to open that order.
5. Review the side column
Customer (name, email, phone, language), Addresses (default address plus the rest of the address book, each with edit, delete and set-as-default), Marketing (Email, SMS and WhatsApp consent), Tax details (Collect tax), Store credit (balance), Payment methods (a count of the customer's saved cards), Notes, and Tags.
- Payment methods only appears once saved cards are set up for your store.
- The Collect tax setting is honoured at online checkout only while this customer is signed in to their own account, and never on a store that prices with tax included — a guest typing their email is still taxed.
6. Delete the record if needed
Use More actions → Delete customer. A customer can only be deleted if they have no orders — if they have any, deletion is refused with "This customer can't be deleted because they have N orders". Deleting can't be undone.
Completion checklist
- The four KPI tiles show real, non-placeholder numbers.
- The Last order card matches the top row of the Orders table.
- Prev/Next navigation moves to the right neighboring customer.
Troubleshooting
Why does RFM group say Prospects for someone who has clearly ordered?
RFM only counts orders that aren't cancelled. A customer whose only order was cancelled, or who hasn't ordered at all, is always scored Prospects.
Why is there no Payment methods card on some profiles?
It is hidden until saved cards are set up for your store. Even then it only shows a count — card numbers stay with your payment provider and are never stored in Lulu. Only the customer can add or remove cards.
Can any staff member edit a customer from this page?
Staff need the customers "Create and edit" permission to see the edit controls (details, addresses, the store credit Edit button). Staff with only "View" can open and read the profile but not change it.
Delete customer gives an error.
Customers who have placed orders can't be deleted, so your order and tax records stay complete. Edit the profile instead to remove details you no longer need.
Add or edit a customer record by hand
Manually create a customer, or update their details, from the admin.
Illustrated guide: lulu.us.com/help/add-and-edit-a-customer
Before you startDecide what contact info you'll use — every customer record needs an email, a phone number, or both.
1. Open Add customer
Go to Customers → Add customer. Enter First name and Last name (both optional), pick a Language (12 are offered — it is saved on the customer record), and enter Email and Phone number.
2. Set marketing consent
Three checkboxes under Marketing consent: agreed to receive marketing emails / SMS marketing text messages / WhatsApp marketing messages. Each stays disabled until its matching contact field (email for the first, phone for the other two) has a value.
3. Add Notes and Tags, then save
Notes are private and never shown to the customer. Add any tags (up to 250, each up to 40 characters). Select Save customer to create the record.
4. Edit an existing record
Open the customer and change fields directly: the Customer card (First/Last name, Email, Phone, Language) in the side column, plus the Marketing, Tax details, Notes, and Tags cards elsewhere on the page.
5. Save your changes
A save bar appears the moment anything changes. Discard reverts to the last saved values; Save writes the change and reloads the profile.
6. Know the two guardrails
Saving fails with “Add an email or phone number to save this customer” if both contact fields end up empty, and reusing another customer's exact email is rejected with “This email is already used by another customer” rather than merged.
Completion checklist
- The new or edited customer has at least one contact method saved.
- A duplicate email is rejected, not silently overwritten.
- Marketing consent only applies to a channel that has a contact value.
Troubleshooting
Can I add a customer with only a phone number, no email?
Yes. Email and phone are each optional on their own — the record just needs at least one of the two.
Why did a marketing-consent checkbox grey out after I cleared a field?
Clearing email auto-unchecks email marketing consent; clearing phone auto-unchecks both SMS and WhatsApp consent. Consent can't outlive the channel it belongs to.
I corrected a customer's email and saving failed.
Another customer in this store already has that exact email. Fix the typo, or edit that existing record instead of trying to reuse its email here.
Use tags and notes on a customer record
Label customers for your own reference and keep private context with their profile.
Illustrated guide: lulu.us.com/help/customer-tags-and-notes
Before you startOpen any customer record — both fields live in the side column.
1. Write a Note
Open a customer → Notes card. Type free text (up to 5,000 characters). It saves with the rest of the profile through the page's Save bar, and the helper text confirms notes “won't be shared with the customer.”
2. Add Tags
Open the Tags card and type a tag, pressing Enter or comma to add it. A customer can carry up to 250 tags, each up to 40 characters.
3. Save
Save the profile with the page's Save bar. Tags and notes are included when you export your customer list to CSV. The customer Import only reads first name, last name, email and phone, so tags and notes aren't brought in by an import.
4. Use tags for your own grouping
Segments can't filter on tags, and the Customers search box matches name, email and phone — not tags. Use tags as labels you see on the profile and in exports, and use the lifecycle stage filter or a segment for list filtering.
5. Set tags at creation time too
The Add customer modal has its own Tags field — tags entered there carry straight through to the new profile, no extra step needed.
Completion checklist
- A note saves and reappears after reloading the profile.
- Tags show on the profile and in a CSV export.
- Neither field is visible anywhere on the storefront.
Troubleshooting
Can I build a segment from a tag?
Not yet. Segments recognise email and SMS subscription, number of orders, amount spent, and country — there is no tag condition.
Will a customer ever see their own tags or notes?
No. Both are internal-only fields that never render on the storefront or in any customer-facing email.
Is there a limit on tags or notes?
Up to 250 tags per customer at 40 characters each; notes cap at 5,000 characters total.
Build a segment with the real filter conditions
The exact conditions the segment query editor understands, and how the live preview works.
Illustrated guide: lulu.us.com/help/segment-filter-conditions
Before you startYou need the "Manage settings" permission to use segments. Know the trait you want to group customers by — conditions are always combined with AND.
1. Open the editor
Customers → Manage segments → Create segment, or open an existing one from the Segments list.
2. Use a filter chip or type a clause
Name the segment, then click a filter chip — Email subscribers, SMS subscribers, Has ordered, Hasn't ordered, Purchased more than once, Spent over $100, In United States — or type directly in the WHERE box.
- email_subscription_status = 'subscribed' (or 'not_subscribed')
- accepts_sms_marketing = true (or false)
- number_of_orders > 1 — counts orders that weren't cancelled
- amount_spent > 100 — net spent (after refunds), in your store currency
- country = 'United States' — the country of the customer's default address
3. Know what the editor understands
Number of orders and amount spent accept =, !=, >, <, >= and <=. Those five condition types are the only ones recognised, and they are always combined with AND. If no clause is recognised, the query is marked unsupported. If at least one clause is recognised, any other text in the query is ignored — so check the preview count rather than assuming every clause was applied.
4. Watch the live preview
The Customers count on the right reruns about 400ms after you stop typing, showing both a count and the percentage of your total customer base that matches.
5. Read the unsupported-query warning
If nothing in the query is recognised, the preview shows "This query isn't fully supported yet" and the count falls back to all customers. Treat that as a sign to fix the query, not as "everyone matches."
6. Save and reuse
Up to four segments appear as tabs above the Customers list (next to All customers and Manage segments); each tab opens that segment's page.
Completion checklist
- Every clause in the query is one of the five recognised condition types.
- The live preview count matches what you expect before saving.
- The segment appears as a tab on the Customers list.
Troubleshooting
Why does my saved segment always show 100% of customers?
Nothing in the query was recognised — for example, tags, lifecycle stage, dates, or a city — so it falls back to counting every customer. Look for the "isn't fully supported" notice and rewrite the query using the supported conditions.
Can I combine conditions with OR?
No. Conditions are always combined with AND. Writing OR doesn't create an either/or segment — the recognised clauses are still all required — so build separate segments instead.
Why don't segment tabs show on the Customers list for some staff?
Segments need the "Manage settings" permission. Staff without it see only the "Manage segments" link above the Customers list, and can't open segments.
Configure customer accounts and sign-in
Control sign-in links, checkout login, self-serve returns, store-credit visibility, and Google sign-in for shopper accounts.
Illustrated guide: lulu.us.com/help/configure-customer-accounts-and-sign-in
Before you startOpen Settings → Checkout and find the Customer accounts card.
1. Show sign-in links in your online store
Toggles the account icon and login links in the storefront header. On by default; turning it off hides the entry point for every shopper, not just guests.
2. Require customers to sign in before checkout
Off by default (guest checkout is allowed). Turning it on forces an account/login step before checkout can complete.
3. Let customers request returns from their account
Off by default. Turning it on lets customers request a return from their order status page (the link in their order emails and account).
4. Let customers see and spend store credit
On by default. Controls whether customers see their store-credit balance and whether it is spent at checkout. When it is on, credit is applied automatically to an order placed with the customer's email (not on orders in another currency). The balance stays on the customer's profile in your admin either way.
5. Let customers sign in with Google
On by default. Adds a "Continue with Google" button to the login and sign-up pages. It uses Lulu's shared Google sign-in, so there's nothing to set up; the optional "Your own Google sign-in client" card below lets you enter your own Client ID and secret so Google's consent screen shows your store's name.
6. Save
This card has its own Save button, independent of the rest of the Checkout settings page.
Completion checklist
- Guest checkout behaves as expected once “Require sign in” is set the way you want.
- The account icon's visibility in the storefront header matches “Show sign-in links.”
- Google sign-in appears or disappears on login/sign-up as the toggle is flipped.
Troubleshooting
Customers say they can no longer check out as a guest.
“Require customers to sign in before checkout” is turned on. Turn it off to restore guest checkout.
The “Continue with Google” button isn't appearing.
Either the toggle is off, or Lulu's shared Google sign-in isn't available yet (a note under the checkbox says so) — in that case, add your own client in the "Your own Google sign-in client" card.
Can I invite a customer to create an account?
Yes. Open the customer in Customers and select Send account invite on the Customer account card; the customer gets a link to choose a password. See send-a-customer-account-invite. These toggles only control the storefront sign-in experience.
Record and manage marketing consent
Track email, SMS, and WhatsApp opt-in per customer, and see how it's enforced elsewhere.
Illustrated guide: lulu.us.com/help/record-marketing-consent
Before you startKnow which consent you actually have permission to record — ticking these boxes is a record, not a collection mechanism.
1. Open the Marketing card
On a customer's profile, the Marketing card has three checkboxes — Email, SMS, WhatsApp — each with a Subscribed or Not subscribed badge.
2. Check the gating
Email is disabled with no email address on file; SMS and WhatsApp are disabled with no phone number on file. You can't record consent for a channel the customer has no contact method for.
3. Tick or untick and save
Use the page's main Save bar. This is the system of record you edit directly — separate from however consent was originally captured at checkout or in a storefront sign-up form.
4. Watch consent clear automatically
Removing a customer's email unchecks email consent in the same save; removing their phone number unchecks both SMS and WhatsApp consent.
5. Filter by consent on the list
On the Customers list, use the email subscription filter (All customers / Email subscribers / Not subscribed), or build a segment with email_subscription_status or accepts_sms_marketing — see Build a segment with the real filter conditions.
6. Check it in your exports
The customer export includes accepts_email_marketing, accepts_sms_marketing and accepts_whatsapp_marketing columns (yes/no). The customer import doesn't read consent columns, so set consent on the profile after importing.
Completion checklist
- A subscribed badge only shows for a channel with a matching contact value.
- Consent clears automatically when its contact method is removed.
- The email-subscribers filter on the Customers list matches what the profile shows.
Troubleshooting
Why can't I subscribe a customer to email marketing?
They have no email address saved. Add one first; later clearing it will unsubscribe them automatically.
Does un-subscribing here stop a message that's already queued?
It stops future marketing sends that check consent; anything already sent or already in flight isn't recalled.
Are SMS and WhatsApp consent the same thing?
No — they're two independent checkboxes and two independent CSV columns, even though both depend on the same phone number.
Import and export your customer list
Bring customers in from a CSV, or download your list for reporting or backup.
Illustrated guide: lulu.us.com/help/import-and-export-customers
Before you startHave a CSV with a header row, or decide which search filter you want to export.
1. Export everything in view
Customers → Export downloads a CSV of the customers matching your current search and filters (or your whole list if none are set). Columns: first_name, last_name, email, phone, accepts_email_marketing, accepts_sms_marketing, accepts_whatsapp_marketing, language, tax_exempt, tags, note, total_orders, total_spent, created_at.
2. Export just a few rows
Select customers with the row checkboxes, then Export selected in the bulk-action bar. This builds a smaller CSV in your browser from the rows already on screen — first_name, last_name, email, phone, location, total_orders, total_spent — and leaves out marketing consent, tags, and notes.
- Export selected can't reach customers outside the current page; change the page size or filter first if you need more.
3. Start an import
Customers → Import. Upload a .csv file or paste CSV text with a header row. Only the first_name, last_name, email and phone columns are read; the file needs an email or a phone column.
4. Run the import
Import up to 1,000 rows at a time. Each row needs an email or a phone number.
5. Read the skip reasons
Rows missing both contacts, or reusing an email already in your store, are skipped — not failed — and listed with a reason (“Missing both email and phone”, “<email> is already used by another customer”). The result banner reads “<n> customers created · <n> skipped”.
6. Fix and re-import
Correct the skipped rows and run Import again. Rows whose email already exists are skipped again, so customers with an email aren't duplicated — but a phone-only row is created again each time, so remove phone-only rows that were already imported before you re-run.
Completion checklist
- The export's filter matches what you intended to download.
- Every created and skipped row in the import result is accounted for.
- Phone-only rows that were already imported are removed before re-running an import.
Troubleshooting
My whole import came back 0 created.
Check the header spelling — first_name, last_name, email, phone (case and spacing don't matter, but the words do) — and confirm every row has at least an email or a phone.
A row failed saying the email is already in use.
That email already belongs to another customer in this store; edit the existing record instead of importing a duplicate.
Can I import addresses or store credit through this?
No — Import only creates customers from first_name, last_name, email and phone. Add addresses, consent, tags and store credit on each profile afterward.
View and set a customer's store credit balance
The store-credit balance on a single customer's profile — separate from gift cards.
Illustrated guide: lulu.us.com/help/manage-customer-store-credit
Before you startTo change a balance you need permission to create and edit customers (to see the Edit button) and the "Edit store credit" permission (to save).
1. Open the Store credit card
On a customer's profile, right column: shows the current balance in your store currency.
2. Edit the balance
Click Edit, type an Amount, and Save. This SETS the absolute balance — it isn't an add/subtract adjustment — so check the current figure before typing a new one.
3. Know the limits
The amount must be zero or more and less than 1,000,000. Each change is recorded with who made it, but there is no store-credit history view on the profile.
4. See it used at checkout
Store credit is applied automatically at checkout, but only while the customer is signed in to the account the balance belongs to — a guest who types that customer's email at checkout isn't given it, and instead sees a prompt to sign in. It isn't spent on orders placed in another currency, and nothing is applied if "Let customers see and spend store credit" is turned off.
5. Don't confuse it with gift cards
Gift cards are separate from store credit and don't show on the customer's profile. Look them up from Products → Gift cards (see Gift cards: issue, manage, and report).
6. Check the storefront toggle
If “Let customers see and spend store credit” (Settings → Checkout → Customer accounts) is off, the balance still exists here, but the shopper won't see or use it on their own.
Completion checklist
- The number you typed is the new TOTAL balance, not an addition.
- The change amount matches what you intended after saving.
- Gift cards for this customer were checked separately, not assumed absent.
- Store credit only reaches checkout for a signed-in customer, never a guest typing the same email.
Troubleshooting
I set $50 but the customer already had $20 — now they show $50, not $70.
Store-credit edits replace the balance outright. Add the old and new amounts yourself before saving if you meant to top it up.
The Edit button is missing on a customer's Store credit card.
The Edit button only shows for staff who can create and edit customers. Saving a new balance also needs the separate "Edit store credit" permission.
Where's the transaction history for store credit?
There is no history view on the profile. Each change is recorded internally with who made it, but it isn't shown on the customer's timeline.
A customer says their store credit wasn't applied at checkout.
Store credit only applies when the customer is signed in to their own account at checkout. A guest who types the same email, or an order in a foreign currency, won't have it applied — the checkout page shows a sign-in prompt in that case.
Track customer activity with the CRM tools
Log notes, calls, and tasks against a customer, assign an owner, and read their activity timeline.
Illustrated guide: lulu.us.com/help/track-customer-activity-and-tasks
Before you startOpen a customer profile — the CRM strip sits just under the KPI tiles.
1. Set Stage, Source, and Owner
Stage: click the badge to pick Lead, Prospect, Customer, Repeat buyer, VIP, At risk, or Churned. Source: click to type a free-text lead source like “Instagram” or “Referral.” Owner: assign any active staff member, or leave Unassigned.
2. Log an activity
In the Log activity card, pick a type tab — Note, Call, Email, Meeting, Task, WhatsApp, SMS — add an optional Title and the Details, then save it.
3. Add task-specific fields
Choosing the Task tab reveals a Due date and an Assign to field (any active staff member, or Unassigned). Tasks created this way appear in the Open tasks list on the same page until someone completes them.
4. Read the Timeline
A single newest-first feed merges every logged activity with “Placed order #… for $…” entries synthesized from their order history, so outreach and purchases interleave in one view.
5. Clean up a mistaken entry
Delete a logged activity (not an order entry) with the delete button next to it in the Timeline, and confirm.
6. Know what doesn't appear here
Changing Stage writes a dated transition to the store's internal event log in the background — it isn't rendered in the visible Timeline card, which only lists CRM activities and orders.
Completion checklist
- Stage, Source, and Owner reflect your latest edit after a page reload.
- A logged Task shows up in Open tasks with its due date and assignee.
- The Timeline reads newest-first and mixes activities with orders correctly.
Troubleshooting
Why don't store-credit changes or lifecycle-stage changes show in the Timeline?
The Timeline card only pulls CRM activities (note/call/email/meeting/task/whatsapp/sms) and orders. Other record changes are written to the store's internal event history but aren't rendered on this card.
An Open task disappeared — did I lose it?
It was marked complete (or deleted). Completed tasks drop out of Open tasks, but the logged activity itself stays visible in the Timeline.
Can I filter the whole Customers list by Stage?
Yes — use the lifecycle stage filter (All stages, Lead, Prospect, Customer, Repeat, VIP, At risk, Churned) on the Customers list.
Handle a customer's data deletion request
What happens when a signed-in shopper asks to have their account deleted, and where to act on it.
Illustrated guide: lulu.us.com/help/handle-a-customer-data-deletion-request
Before you startThis is distinct from publishing a privacy policy (see Policies and privacy) — it's about acting on one specific customer's request.
1. Know where the request comes from
A signed-in customer can ask for deletion from their own account (Account → Profile → the danger-zone request). Lulu never deletes anything automatically. Orders, payments, tax records, and gift-card or loyalty history usually have to be retained, so the decision and the action stay with you.
2. Get notified
The request appears under Customers → Privacy requests (Pending tab, with a due-date badge) and an email ("Account deletion requested by a customer on <store>") goes to your staff notification recipients: the addresses under Settings → Notifications → Staff notifications → Additional recipients, or the store owner if that list is empty.
3. Review before acting
Click Review on the request to open the customer, and check their order, store-credit, and loyalty history.
4. Erase or decline
To act on it, follow Erase a customer's personal data: More actions → Erase personal data keeps your order and tax records but removes the personal details. To refuse, click Decline on the request and give a reason.
5. Installed apps are told for you
When you erase a customer, installed third-party apps that can see customer or order data are notified automatically so they can delete their copy too. To see this, go to Customers → Privacy requests → Completed, find the request, and click Apps notified.
6. Expect one open request at a time
A customer can only have one pending deletion request open. Asking again while one is pending returns “You've already asked for your account to be deleted”. After a declined request, they can ask again.
Completion checklist
- The request shows on Customers → Privacy requests and the email reaches your staff recipients.
- You checked retention obligations (orders, tax, payments) before erasing.
- You erased or declined each request, and checked Apps notified afterwards.
Troubleshooting
A customer says they asked for deletion but nothing happened.
Nothing is deleted automatically. Check Customers → Privacy requests for the pending request, and that the email reached your staff notification recipients (and your spam folder).
Can I delete a customer who has orders?
Not with Delete customer. Use Erase personal data instead: it removes the personal details and keeps the orders, anonymised, for your sales and tax records.
An app shows Failed under Apps notified.
The app's privacy endpoint didn't accept the notice after repeated attempts. The data in Lulu is erased. Contact the app's publisher and ask them to delete that customer's data.
Send a customer an account invite
Email a customer a one-time link to activate their account and choose a password, then resend it or see when it expires.
Illustrated guide: lulu.us.com/help/send-a-customer-account-invite
Before you startOpen Customers and choose a customer who has an email address. You need the Send account invite staff permission (a role that can edit customers needs it added). Erased customers cannot be invited.
1. Open the customer and find the Customer account card
Go to Customers and open the customer. On the profile page, look for the Customer account card. It is not shown for a customer whose personal data was erased.
2. Read the account status
The card shows one of three states.
- No account: "This customer hasn't set up an account yet." The button reads Send account invite.
- Invited: "Invite sent <date>; the link works once and expires <date>." The button reads Resend invite.
- Active: "This customer has an account and can sign in." No button is shown.
3. Send the invite
Select Send account invite. A toast confirms Invite sent and the card changes to Invited. The button is disabled if the customer has no email ("Add an email address to send an invite.") or if you have unsaved edits on the page ("Save your changes first.").
4. What the customer receives
The customer gets the Account invite email with a link to an Activate your account page on your own storefront address (your custom domain if you have one), never the admin. The link works once and expires 30 days after it was sent.
5. The customer activates the account
The customer opens the link, enters a Password (at least 8 characters) and the same value under Confirm password, then selects Activate account. They are signed in straight away and land on their account page, and their email address is marked as verified.
6. Resend an invite
If the customer lost the email or the link expired, open their profile and select Resend invite (or Send account invite). A new link is sent and the old one stops working immediately. You can send at most one invite per customer every 2 minutes.
7. Change the wording of the email
Go to Settings > Notifications, open Customer accounts > Account invite and edit the subject and HTML. This email is always on (it has no Send this email switch) because the invite is something you chose to send. See customize-notification-emails.
Completion checklist
- The customer has an email address and you saved the profile first.
- You see the Invited state with the expiry date after sending.
- The customer chose a password and now shows Active.
- You resend rather than forward the old link if it expired.
Troubleshooting
The customer says the link is invalid or expired.
Links work once, expire after 30 days and stop working as soon as you send a newer invite. Open their profile and select Resend invite; ask the customer to use the newest email.
The page says "This invite was already used".
The customer already activated the account. Ask them to sign in, or use the "forgot password" link on the sign-in page.
I changed the customer's email after inviting and the link stopped working.
An invite is tied to the address it was sent to. Send a new invite to the new address.
There is no Send account invite button.
Check that you have the Send account invite permission, that the customer has an email address, and that they are not erased. A customer whose sign-in is managed by a marketplace seller account cannot be invited either.
I get "Couldn't send the invite email".
The email could not be handed to your email provider, so no invite was recorded. Try again in a moment, and check your email delivery settings (email-delivery-and-test-send).
Buy a new domain through Lulu
Search for an available domain, see the price, and register it without leaving your Lulu admin.
Illustrated guide: lulu.us.com/help/buy-a-domain-through-shopwise
Before you startYour store already has a free subdomain ({your-handle}.lulu.us.com) that works without any setup. Buying a custom domain is optional and gives your store an address like yourbrand.com. When you buy, you pay for the first year of registration only. Renewal isn't charged automatically, but Lulu emails you a reminder before it expires.
1. Open Domains
Go to Settings > Domains in your Lulu admin. You'll see your free managed subdomain at the top (always shown as Managed and Connected), followed by any custom domains you've already connected, transferred, or bought.
2. Start the Buy a new domain flow
Click the Buy a new domain option in the three-option hub (the other two are Connect existing domain and Transfer your domain). A search box opens.
3. Search for a name
Type the name you want (for example yourbrand) and click Search. Each domain in the results shows an Available or Taken badge. Available domains show a price per year and a Buy button.
- If domain registration isn't turned on for your store yet, this screen shows "Buying domains isn't available yet. You can still connect or transfer a domain you own."
4. Confirm the registration
Click Buy next to the domain you want. The Confirm registration dialog shows the domain and its price per year. It also confirms that the first year of registration is included (renewal isn't charged automatically yet), that WHOIS privacy is included at no extra cost, and that the domain is connected to your store automatically once it's registered.
5. Pay for the domain
Click Confirm & pay. A secure payment window opens, and registration starts as soon as the payment is confirmed. If your account is billed by invoice, the button says Confirm & register instead. The domain registers straight away and the charge goes on your store invoice (Settings > Billing). If payments are temporarily unavailable, the dialog says so and the button is disabled until you try again.
6. Watch the purchase complete
While a purchase is in progress, it appears above your domain list with a status badge: Awaiting payment, Registration in progress, We're checking this payment, We're checking this registration, or (rarely) Paid — not registered, refund due. The page checks automatically. Once the domain is registered, it's added to your domain list with ownership already verified. If you didn't have a primary custom domain yet, it becomes your primary domain. The SSL certificate is issued shortly after.
Completion checklist
- Search for your domain name from Settings > Domains > Buy a new domain
- Confirm the per-year price before paying
- Complete payment (card popup) or confirm invoice billing
- Wait for the status badge to clear as the domain registers
- Watch for Lulu's 30- and 7-day reminder emails as the year ends, and contact support to renew before then, because renewal isn't charged automatically
Troubleshooting
The domain I searched for shows as Taken. What can I do?
Try a different name, extension, or variation — the search returns suggestions alongside an exact match for the term you typed. If you already own that exact domain, use Connect existing domain or Transfer your domain instead of buying it again.
My purchase shows "We're checking this payment" — did I get charged?
It means Lulu is confirming the payment with the payment provider before registering the domain. Leave the page open or come back later, and it updates on its own. If you were charged but the domain can't be registered, the status changes to "Paid — not registered, refund due". Contact support and they'll arrange the refund.
Why can't I buy a domain?
Domain buying can be switched off for every store, for example while registration is paused. When it's off, the Buy a new domain screen says buying isn't available, but you can still connect or transfer a domain you already own. Each store can also register at most 2 domains a day.
Will Lulu renew my domain automatically next year?
No. What you pay at purchase covers one year of registration, and there's no automatic renewal charge. Lulu emails you a reminder 30 days and 7 days before your domain expires, and once more if it lapses — contact support when you get the first reminder rather than waiting for the last one, since renewal itself is still handled by the Lulu team.
Connect a domain you already own
Point a domain you bought elsewhere (GoDaddy, Namecheap, or any registrar) at your Lulu store with two DNS records — www and the root domain — and follow DNS, propagation and SSL from the same screen.
Illustrated guide: lulu.us.com/help/connect-an-existing-domain
Before you startYou need to be able to sign in at your domain's current registrar or DNS host to add records. Lulu has no fixed IP address for your store, so you never add an A record — you point www (and, if your provider allows it, the root domain) at Lulu's routing host instead.
1. Open the Connect flow
Go to Settings > Domains and click Connect existing domain. Enter the domain exactly as you own it — the bare domain (yourbrand.com), www.yourbrand.com, or a subdomain such as shop.yourbrand.com — and click Continue. When you enter yourbrand.com or www.yourbrand.com, Lulu connects both addresses together and gives each its own SSL certificate.
2. Let Lulu detect your provider
Lulu looks up the domain's nameservers and, when it recognizes the provider (for example GoDaddy or Namecheap), shows "We detected {provider}" with a link to open that provider's DNS dashboard directly. If the provider isn't one Lulu recognizes, it shows "Set up your DNS records" instead and you'll add the records manually at whatever host you use.
3. Use one-click setup if it's offered
For a small number of providers that support the Domain Connect standard and the exact template Lulu can use, a "Connect automatically" button appears. Clicking it sends you to your provider to authorize the change, and the required records are added for you. Most providers don't support this yet, so the manual records table below is the normal path.
4. Add the DNS records manually
Under step 1, Configure DNS records, Lulu lists the records to add in a table with Type, Name, Current values and Update to. The Name column uses the short names DNS providers expect (@ for the root domain, www, shop); hover it or read the line under it for the full name. Current values shows what the internet sees today — (empty) when nothing is set yet. Use the Copy button next to each value, remove any other record with the same name and type, then click I updated DNS records.
- CNAME record — Name www, value the routing host shown (for example shops.<platform domain>). Always add this one; it is enough on its own for your store to work.
- ALIAS, ANAME or flattened CNAME record — Name @ (your root domain), same value. If your DNS provider doesn't offer ALIAS, ANAME or CNAME flattening for the root domain, set up domain forwarding (redirect) from yourbrand.com to https://www.yourbrand.com at your provider instead.
- Subdomain such as shop.yourbrand.com — one CNAME record, Name shop, same value.
- CNAME record for admin.<yourdomain> — marketplace stores only.
- TXT record _shopwise-challenge — optional. Only needed if you can't change the records above yet; it proves you own the domain.
5. Follow the three steps until everything says Done
The panel shows your domain with a status badge — Needs setup, Connecting, Connected or Action needed — and three steps: Configure DNS records, DNS propagation, and TLS certificate. Each step shows Done (green tick), Waiting… (amber clock, with what it's waiting for) or Problem (red cross, with the exact reason, for example "www still points to 203.0.113.5"). These are status indicators, not buttons. The panel rechecks every 30 seconds while it's open; click I updated DNS records or Check again to check straight away. DNS changes can take up to 48 hours to spread, though it's usually much faster. The SSL certificate for every address (root, www, and admin for marketplaces) is requested automatically. If you forward the root domain to www at your provider, only www needs a certificate — the panel says so and that's fine.
6. Make it your primary domain
When the domain shows Connected (or at least DNS ✓) in Settings > Domains, click Set as primary on its row. For a bare domain, Lulu makes www.yourbrand.com the primary address by default and redirects yourbrand.com to it — this works whether you used an ALIAS record or forwarding. If you set up the ALIAS record, you can switch the primary to the bare domain in the domain's panel (Use yourbrand.com instead). All your other connected domains redirect visitors to the primary domain.
Completion checklist
- Enter the exact domain in Settings > Domains > Connect existing domain
- Check whether one-click Domain Connect is offered for your provider
- Add the CNAME record for www, and an ALIAS/ANAME/flattened CNAME for @ (or forward the root domain to https://www.yourdomain)
- Click I updated DNS records, then wait for all three steps to show Done
- If the domain is already being set up in another store, add only the TXT record shown to prove you own it, then the other records
- Click Set as primary once the domain is verified
Troubleshooting
It says the domain is already being set up in another store.
Someone added this domain to another store but never finished connecting it. If the domain is yours, you can still connect it. The panel shows a single TXT record named _shopwise-challenge that holds a code unique to your store. Add only that record at your DNS provider and don't change your other DNS records yet, then click I updated DNS records. As soon as Lulu sees your TXT record, the domain is removed from the other store and connected to yours, and the panel then shows the records that send visitors to your store. The other store is told the domain was removed, but not who connected it. If the TXT record isn't found within 14 days, the request lapses and you can start again. A domain that another store has already finished connecting can't be taken over this way — contact support.
My DNS provider won't accept a hostname in an A record for the root domain.
That's correct — an A record can only hold an IP address, and Lulu doesn't use one. Add the www CNAME record, then either an ALIAS, ANAME or flattened CNAME record for @, or set up domain forwarding (redirect) from your root domain to https://www.yourdomain at your provider. With forwarding, your store runs on www and the root domain sends visitors there.
Step 1 says Problem and shows an old value.
The Current values column shows what the internet sees today. If www or @ still points to your old host (an IP address or another hostname), delete that record at your provider and add the one shown under Update to. Then click I updated DNS records.
DNS is Done but DNS propagation or the TLS certificate is still waiting.
DNS changes can take up to 48 hours to spread, and the certificate is only issued once your addresses reach Lulu — usually a few minutes after propagation. The TLS step shows the certificate's current state in plain words. If it says the validation or issuance timed out, check the records and click I updated DNS records to request it again. If it stays waiting for more than a day after DNS is working, contact support.
Do I still need the _shopwise-challenge TXT record?
No, not if your www (or subdomain) CNAME points to Lulu — that already proves you own the domain. The TXT record is optional and only helps if you can't change the other records yet — unless the panel says this domain can only be verified with the TXT record (for example, when it's already being set up in another store). Domains that were verified with a TXT record keep working.
Can I remove a domain and reconnect it later?
Yes. Click Remove on the domain's row in Settings > Domains to disconnect it. This removes both the root and www addresses. If it was your primary domain, your store goes back to its free subdomain. You can add the same domain again later.
I don't see a "Connect automatically" button for my provider.
One-click setup only appears when Lulu detects a provider that supports the Domain Connect standard with a published, approved template. It adds the same records as the table. For most providers today, adding the records manually is the normal and fully supported path.
My domain is connected, but visiting it shows a different address.
That's expected: every connected domain redirects visitors to your primary domain, the same way Shopify does. If you haven't chosen a primary domain yet, connected domains redirect to your store's free address instead. To change which address is primary, click Set as primary on the domain you want, or use the switch in the domain's panel for root versus www. To keep a domain showing its own address, change its type to Alias.
Transfer a domain into Lulu
Move a domain you own at another registrar so it's managed inside Lulu, using your domain's authorization (EPP) code.
Illustrated guide: lulu.us.com/help/transfer-a-domain-into-shopwise
Before you startYour domain must be unlocked at its current registrar, be more than 60 days old, and be outside any transfer-lock period. You'll need its authorization (EPP) code. The Lulu team processes your request with the registry, which can take up to 7 days. You don't have to wait for the transfer to finish before using the domain, because you can connect it at the same time.
1. Unlock your domain at its current registrar
Sign in at your current registrar and turn off the transfer lock (sometimes called registrar lock) on the domain. Request the authorization code, often called an EPP code or auth code — your registrar emails or displays this.
2. Open Transfer your domain
In Lulu go to Settings > Domains and click Transfer your domain.
3. Submit the domain and code
Enter the Domain exactly, then paste the code into Authorization (EPP) code. The code is required, and the form won't submit without it. Click Start transfer. The code is stored encrypted and is only used to complete the transfer.
4. Keep your store live while you wait (optional)
A banner in the Transfer modal offers "connect this domain" so you can point DNS at Lulu and start using the domain immediately, while the registry transfer completes separately in the background.
5. Track transfer status
The Transfers in progress list at the bottom of the Transfer your domain dialog shows each request and its status: Requested, Submitted, Pending at registry, Completed, Failed or Canceled. The Lulu team moves the request through these stages with the registry, so they don't change instantly.
6. Cancel if needed
While a transfer is Requested, you can click Cancel next to it to withdraw it. Once it has been submitted to the registry, you'll need to contact support to cancel it.
Completion checklist
- Unlock the domain and get its authorization (EPP) code from the current registrar
- Confirm the domain is more than 60 days old and not already being transferred
- Submit the domain and code from Settings > Domains > Transfer your domain
- Optionally connect the domain at the same time so your storefront isn't waiting on the transfer
- Check the Transfers in progress list for status updates
Troubleshooting
I don't have the authorization code yet — can I still start?
No. The form needs the Authorization (EPP) code before it will submit. Ask your current registrar for it first. In the meantime, you can use connect this domain to point the domain at your store.
My transfer has been stuck on the same status for a while.
Transfers can take up to 7 days and move through Requested, Submitted, then Pending at registry. If it sits on one status well past that window, contact support with the domain name and they can check it with the registry.
Is my authorization code safe?
Yes — Lulu encrypts the authorization code at rest and never logs or emails the plaintext value. It's used only to complete the registry transfer.
Why was my transfer request rejected?
A transfer is refused if the domain is a Lulu subdomain (these can't be transferred), if the domain name isn't valid, or if your store already has a transfer in progress for the same domain.
Manage your domains: primary domain, free subdomain, and removal
Understand your store's free managed subdomain, choose which domain customers see, and remove a domain you no longer need.
Illustrated guide: lulu.us.com/help/manage-your-domains
Before you startThis article assumes you already have at least one custom domain connected, bought, or transferred — see the other domains articles if you don't yet.
1. Know your free subdomain
Every Lulu store always has a free subdomain in the form {your-handle}.lulu.us.com, shown at the top of Settings > Domains with Managed and Connected badges. It works with no setup and can't be deleted — it's what your store falls back to if you remove your primary custom domain.
2. Review your connected domains
Below the free subdomain, each custom domain shows its hostname (with its www or root partner when you connected a bare domain), a type badge — Primary, Redirecting or Alias — for the domain and for its www or root partner, and a status badge: Connected, Connecting, Needs setup or Action needed. Under it, a health line shows DNS (✓ or what needs changing), SSL (✓ or the certificate's current state), whether it's primary, redirects to your primary domain or is an alias of it, and when it was last checked. Click the domain name or View status at any time to open the full status panel — the records with their current values and the three setup steps — for example if a DNS change at your provider later breaks something.
3. Check expiry and auto-renew status
A domain you bought through Lulu also shows its expiry (or renewal) date and its registrar auto-renew status — on, off, or unknown — on its row, with a days-left badge once it's within 30 days of expiry. Lulu checks the registrar regularly and emails you reminders 30 and 7 days before it expires, and once more if it lapses, so a renewal doesn't come as a surprise — renewing it is still a request to the Lulu team, not an automatic charge. A connected or transferred-in domain doesn't show this, since Lulu isn't its registrar.
4. Set a domain as primary
Click Set as primary on any domain with DNS ✓, or open the domain and use Change in its Domain target and type card. Your storefront's address bar then shows that domain. The previous primary domain stays in your list as a redirecting domain: visitors who type it are sent to your new primary domain. To serve your store on a domain without redirecting, make it an alias domain instead — see Change a domain's type.
5. Reopen a domain's connection details
Click Manage on any domain to reopen its DNS records table and connection status checklist — useful if you need to double-check a record or re-trigger verification.
6. Remove a domain
Click Remove on a domain you no longer want. If it was your primary domain, your store goes back to the free {your-handle}.lulu.us.com subdomain, so it always has a working address.
Completion checklist
- Remember your free {handle}.lulu.us.com subdomain always works as a fallback
- Check each domain's status badge and health line (DNS, SSL, last checked) before relying on it
- Set your preferred domain as primary once it's verified, because only the primary domain serves your store
- Remove domains you no longer use
- Watch the expiry/auto-renew line and the 30- and 7-day reminder emails on any domain bought through Lulu
Troubleshooting
Can I have more than one custom domain connected at once?
Yes. You can add several domains (connected, bought or transferred), but only one can be Primary at a time. Every other verified domain is a redirecting domain by default: visitors are sent to your primary domain. You can change any of them to an alias domain, which shows your store without changing the address bar — see Change a domain's type.
I removed my primary domain by mistake — is my store down?
No. Removing the primary domain automatically falls back to your free {your-handle}.lulu.us.com subdomain, so the storefront keeps working while you reconnect or choose a new primary domain.
Why can't I set a domain as primary?
Only a domain with DNS ✓ (verified) can be made primary, so the Set as primary button only appears once it's verified. Finish connecting it first: add the DNS records and wait for Ownership verified.
A domain's expiry line says the date isn't available yet.
Lulu checks the registrar regularly for domains bought through the platform; until that check succeeds you'll see a note that it checks regularly and emails you 30 and 7 days before expiry. This expiry/auto-renew line only appears for domains bought through Lulu — a connected or transferred-in domain shows its DNS and SSL status instead.
Change a domain's type: primary, redirecting or alias
Choose what each of your domains does: show your store as the main address, send visitors to your primary domain, or show your store without redirecting.
Illustrated guide: lulu.us.com/help/change-a-domains-type
Before you startYou need at least one connected domain whose DNS is verified (DNS ✓). Each address is set on its own — if you connected a bare domain such as yourbrand.com, the root and the www address each have their own type.
1. Learn the three domain types
Every connected domain has one type. A primary domain is the address shown in the browser's address bar while visitors browse your online store — your store has exactly one. A redirecting domain sends visitors to your primary domain, so they always end up on one address; this is the default for every other domain. An alias domain shows your online store on its own address without redirecting or changing the address bar.
- Primary domain — displayed in the address bar when visitors are browsing your online store
- Redirecting domain — directs visitors to your primary domain
- Alias domain — displays your online store but doesn't redirect or update the address bar
2. Open the domain
Go to Settings > Domains and click the domain name, or click View status or Manage on its row. At the bottom of the panel, the Domain target and type card shows Target: Online Store and the current Type for each address — for example Primary domain, Redirects to yourbrand.com, or Alias of yourbrand.com. A bare domain and its www partner are listed separately. If your store has no primary custom domain yet, a redirecting domain shows Redirects to followed by your store's free address — visitors are sent there — and an alias domain shows your store on its own address.
3. Click Change
Click Change next to the address you want to update. The Change domain type dialog opens with the three options, and the current one is marked (Current). The Change button only appears once the domain's DNS is verified.
4. Pick the new type and confirm
Select Primary domain, Redirecting domain or Alias domain, then click Change domain type. The button stays disabled until you pick a different type. When it's saved you'll see a confirmation and the domain list updates its Primary, Redirecting or Alias badge.
5. Make a different domain primary
Choosing Primary domain on another address makes it your store's main address in one step. Your old primary domain becomes a redirecting domain automatically, so links to it keep working.
Completion checklist
- Keep exactly one primary domain — the address you want customers and search engines to see
- Leave other domains as redirecting domains unless you have a specific reason to use an alias
- Use an alias domain sparingly: it shows the same pages on a second address
- Make another domain primary before changing your current primary domain's type
Troubleshooting
Why can't I change my primary domain to redirecting or alias?
Your store always needs one primary domain. Open the domain you want to use instead, click Change and choose Primary domain. Your old primary domain then becomes a redirecting domain, and you can change it to an alias afterwards if you want.
Why is the Primary domain option greyed out for my root domain?
Your DNS provider forwards the root domain (for example yourbrand.com) to the www address instead of pointing it at your store, so it can't be the primary address — visitors would loop. Use the www address as primary, or replace the forwarding with the ALIAS, ANAME or flattened CNAME record shown in the panel and check again.
Does an alias domain hurt my search ranking?
It can if it's misused, because the same pages are shown on more than one address. To limit that, pages served on an alias domain tell search engines that your primary domain is the main copy (a canonical link), and the alias domain's sitemap lists your primary domain's pages. A redirecting domain is still the safest choice for most extra domains.
I don't see a Change button.
The Change button appears only for addresses whose DNS is verified. Finish connecting the domain first: add the DNS records shown in the panel and click I updated DNS records.
My domain redirects to my store's free address.
Your store doesn't have a primary custom domain yet, so redirecting domains send visitors to your store's free address. Choose Primary domain for the address you want customers to see, and the other domains will redirect there instead. To show your store on a domain without redirecting, change its type to Alias domain.
Finish your store's setup guide
Work through the checklist on Home that tracks the handful of settings every store needs before it can take an order.
Illustrated guide: lulu.us.com/help/finish-your-setup-guide
Before you startSign in to your store's admin. The setup guide shows on Home to any staff member who can view Home, and reflects your store's real settings — not a generic tour.
1. Find the setup guide on Home
Open Home in your admin. While your store still has unfinished required settings, a "Set up your store" card appears below the page header with a progress bar, a line reading "N of M complete", and a list of what's left. Each item links straight to the place where you fix it.
2. Set up payments
Click "Set up payments" to go to Settings → Payments and turn on at least one payment method. Until one is on, customers can't pay at checkout.
3. Add a shipping rate
Click "Add a shipping rate" to go to Settings → Shipping and add at least one rate so orders can be delivered.
4. Add a contact email and your first product
"Add a contact email" opens Settings → General, where you enter the store contact email customers can reach you at. "Add your first product" opens the new-product form — the check only passes once at least one product has status Active. Draft or archived products don't count.
5. Finish with Go live
"Go live" is the last item on the list and only turns green once your store has been switched to production. It links straight to the Go live page.
6. Dismiss or come back later
"Dismiss" hides the card for the current browser session only — it isn't saved to your account. Open the admin in a new session and the card comes back for as long as any item is still incomplete. Once every item is done, the card disappears on its own.
Completion checklist
- Set up payments
- Add a shipping rate
- Add a contact email
- Add your first product
- Go live
Troubleshooting
I dismissed the setup guide — did that mark it as done?
No. Dismiss only hides the card for your current browser session. It reappears the next time you open Home if any item is still incomplete, and disappears for good only once every item is done.
I already have products, but "Add your first product" still shows as unfinished.
Before your store has ever gone live, Home can offer a choice between setting up yourself or hiring an onboarding partner. Choosing "Set up myself" is remembered on this device and the card won't come back; "Choose a partner" takes you to the onboarding partner directory.
A card offering a setup partner appeared before the checklist. What is that?
Yes — anyone with permission to view Home sees it. Some of the pages it links to (like Payments) need the matching settings permission, so a staff member without it may not be able to make the change.
Can staff other than the owner see the setup guide?
Yes — anyone with permission to view Home sees it, but some of its links (like Payments) may be unavailable to staff without the matching settings permission.
Development and production mode
Understand the difference between a development store, which can only take test payments, and a production store, and why Lulu won't let you flip the switch yourself the first time.
Illustrated guide: lulu.us.com/help/development-and-production-mode
Before you startEvery new store starts in development mode. Mode is related to, but separate from, the storefront password — see manage-store-access for the password itself.
1. Check your current mode
Open Settings → Plan. The first card shows a "Development store" badge while you're in development, with a line explaining that the store can only process test payments until it switches to production.
2. Know what development mode restricts
In development mode, checkout uses a test gateway ("Bogus Gateway (for testing)" on the Payments page): no real money is charged and every order is tagged test. Real gateways such as PayPal show a note that they stay dormant until the store switches to production.
3. Try switching to production directly
The "Store status" card on Settings → Plan offers Development and Production with a Save button — but while your store has never gone live, saving Production is refused with "Use Go live to take your store online". Online Store → Preferences shows a Go live button in its Store status card instead of the toggle until then.
4. Go live the first time
Run the Go-live checklist instead. The first switch to production only happens there, because it also confirms your plan is paid, your apps are paid for, and you can actually take payments.
5. Switch modes afterward
Once your store has gone live once, the Development/Production choice in Settings → Plan (and in Online Store → Preferences) becomes an ordinary switch. Switching to production also turns the storefront password off. Use development for maintenance — for example, to test something without risking a real charge — then switch back to production when you're done.
Completion checklist
- Development mode only ever processes test payments, never real ones
- The first switch to production must go through Go live, not the Settings toggle
- After your first launch, switching modes in Settings is unrestricted
- Switching back to development with password protection on re-gates your storefront
Troubleshooting
I picked Production in Settings → Plan and got "Use Go live to take your store online."
That's expected the first time: a store that has never launched can't flip to production from a settings toggle. Use the Go live page instead — it runs the same check and actually turns the switch on once everything passes.
Will switching back to development stop real payments?
Yes — in development mode checkout always uses a test gateway, so don't switch an already-live store back to development while you expect to take real orders.
If I switch back to development and turn Enable password on, what happens?
Going back to development plus turning the password toggle on re-gates your storefront behind a password page again, exactly as a brand-new store is gated. If your store sells through a marketplace, this also drops it from marketplace listings until it's reopened.
Does switching modes affect my orders or products?
No — the mode only governs which payment gateway checkout uses (test vs. real) and whether the storefront is gated. Your products, orders, and settings are unaffected.
Use the Go-live checklist
Walk through the five checks on the Go-live page — plan, paid apps, theme, payments, and domain — and take your store from development to production.
Illustrated guide: lulu.us.com/help/go-live-checklist
Before you startOpen the Go live page from Home (the "Go live" item in the setup guide) or from Settings → Plan → "Run the Go-live checklist". Any staff who can see Home can view the page, but paying for apps and going live need permission to manage the plan.
1. Open the checklist
While your store is still in development, the page explains that only people with the storefront password can see it, and that finishing the checklist switches it to production. If a paid app's payment is due, it also shows how much.
2. Read the five checks
The Checklist section lists: Store plan (paid and renewing in the future), Paid apps (no installed app still due for payment), Theme (you have a live theme, and it is free or a paid theme you own), Payments (at least one payment method is on), and Custom domain (optional — you can launch without one). Each item that isn't done has a Fix (or "Set up") link.
- Store plan
- Paid apps
- Theme
- Payments
- Custom domain (optional)
3. Pay for apps that are due
A paid app plan starts the app's normal free trial and bills when it ends, whether or not your store is live. An app whose trial is still running is not charged when you go live. The Paid apps table lists each app that is due, with its plan and price; click "Pay $X for apps" to pay for them one at a time in a secure payment window (each then renews on its own 30-day cycle). If your store is on a monthly bill, the button reads "Add $X to my monthly bill" instead — nothing is charged that day and the apps go on your next bill.
4. Resolve a paid theme
If your published theme is paid and this store hasn't bought it, the Theme check blocks launch and shows its price. Buy it from Online Store → Themes, or publish a free theme instead.
5. Go live
Once every non-optional check passes, the panel at the bottom reads "You are ready" and the "Go live" button becomes active. Clicking it removes the password page, opens your storefront to everyone, and opens the live store in a new tab.
6. Revisit after launch
Come back to the Go live page later and you'll see "Your store is open" with the date you went live, plus links to visit the store or open Store preferences, instead of the checklist.
Completion checklist
- Plan is paid and renewing
- Every installed paid app is paid for, or still in its free trial
- The live theme is free, or paid and owned
- At least one payment method is on
- Custom domain connected (optional)
Troubleshooting
Why am I being charged for apps I installed weeks ago?
A paid app plan starts the app's normal free trial (usually 14 days), then bills, whether or not your store is live. When the trial ends, the app is due. Going live never charges an app whose trial is still running.
The Go live button is disabled.
When the store isn't ready, the panel above the button reads "Not ready yet" and lists the checks that still fail by name. Fix those first — the optional custom domain check never blocks the button.
Do I need a custom domain to go live?
No. Custom domain is the only optional item — you can open on your store's own address and connect a custom domain any time afterward from Settings → Domains.
A payment for one of my apps failed during Go live — did it charge the others too?
No. Apps are paid one at a time in a secure payment window, so one failure never affects the rest. If a payment fails or you close the window, that app simply stays due and you can press Pay again.
Switch between stores on one account
If you own more than one Lulu store with the same email and password, move between them without logging out or re-entering your password.
Illustrated guide: lulu.us.com/help/switch-between-your-stores
Before you startThis applies when your email and password give you access to two or more active stores. Switching from inside the admin is available to store owners.
1. Sign in once at the central login
At the central login page, enter your email and password. If that combination signs you in to more than one active store, you'll see a chooser listing each store by name before you land in any one admin — you don't repeat your password to pick between them. If any of those stores requires two-step verification, you'll be asked for the emailed code first.
2. Come back to the chooser without retyping your password
The chooser is remembered for about five minutes after you sign in, so refreshing the page doesn't send you back to the login form.
3. Switch stores from inside the admin
As an owner, open the store and account menu in the top-right of any admin page. The stores section lists the store you're in (with a checkmark) and the other stores you own that were verified for this sign-in or are linked to it.
4. Pick another store
Click any other store in the list. Lulu signs you into that store's admin directly through a one-time handoff link — no password prompt.
5. Create an additional store
The same menu has a "Create store" link, which opens signup with your email filled in so you can choose a package and pay for a new, fully independent store.
Completion checklist
- One sign-in with the same email and password can reach several stores
- No password re-entry needed to move between stores you own
- Each store keeps its own data, staff, and settings — nothing is shared
Troubleshooting
A store I expect to see isn't in the switcher.
The switcher only lists stores where you are the owner and whose access was confirmed with the same credentials when you signed in (or that are linked). If a store uses a different password for you, or you're staff rather than the owner there, sign in to it separately.
Clicking another store in the menu sent me to a login page instead of straight in.
The one-time handoff occasionally can't complete (for example, a blocked redirect). You're then sent to that store's admin address, which asks you to sign in there as usual.
Is this the same as Linked stores?
No. Linked stores (Linked stores page) groups stores together to sync products and pull combined reports across a multi-country brand. Switching stores is only about one login reaching several otherwise-independent store admins — it doesn't connect their data at all.
Search your admin
Jump straight to any page, setting, product, order, or customer from one search box instead of clicking through the menu.
Illustrated guide: lulu.us.com/help/search-your-admin
Before you startSign in to your store's admin. Search is available on every admin page once you're signed in.
1. Open search
Click the Search box in the top bar, or press Ctrl+K on Windows/Linux or ⌘K on a Mac from anywhere in the admin.
2. Type to search
Results appear grouped as you type: "Pages & settings" first, then matching Products, Orders, and Customers (up to five of each).
3. Search by what you know
Search orders by order number, customer name, or email; customers by name, email, or phone; and products by title, handle, or vendor. The result opens the record itself, not just the list.
4. Pick a result
Use the arrow keys and Enter, or click, to open the page or record you found.
5. Use it on a phone
On narrow screens the Search box collapses to a magnifying-glass icon in the top bar; tap it to open the same search.
Completion checklist
- Ctrl+K (⌘K on Mac) opens search from any admin page
- Search covers pages, settings, products, orders, and customers together
- Product search matches title, handle, and vendor
Troubleshooting
Ctrl+K doesn't open anything.
Click directly on the Search box in the top bar instead. If you're focused inside another input or a modal, that field may be capturing the keystroke first.
I can't find an order by its number.
Make sure you're searching from the store whose order it is — switch to that store first if you manage more than one.
Search shows pages but no products, orders, or customers.
Record results arrive a moment after page results, and they only appear for areas your staff account has permission to view. Product search matches title, handle, and vendor — not SKU; to find a product by SKU, use the search on the Products page or Inventory page.
Your free trial
How Lulu's introductory offer works on Basic, Grow, and Advanced: a short free trial, then a discounted price, before the regular rate begins.
Illustrated guide: lulu.us.com/help/your-free-trial
Before you startThe free trial only applies where Lulu is showing it at signup or on your Billing page — it isn't guaranteed for every store, plan, or payment method. See choose-a-package first if you haven't picked a plan yet.
1. Check whether you're on the offer
Open Settings → Billing. While you're in the trial, a banner reads "You're on a free trial until <date>", with a Cancel plan button — cancel before that date and you won't be charged.
2. Know which plans qualify
Basic, Grow, and Advanced all get a 3-day free trial. Plus (the custom plan) is never eligible for the offer.
3. Know what happens after the trial
On a monthly plan, the 3-day trial is followed by three 30-day cycles billed at $1 each, then your plan's regular monthly price. On a yearly plan, you only get the 3-day trial — after that you're charged the regular yearly price straight away.
4. See your exact dates
The trial banner and the Billing page both show the date your trial ends, and — for a monthly plan — when the $1 cycles end and the full price starts.
5. Avoid ending the offer early
Changing your plan — upgrading or downgrading — while you're still in the trial or the $1 cycles ends the offer immediately. The confirmation dialog shows this warning and what you'll be charged before you confirm.
Completion checklist
- Basic, Grow, and Advanced qualify; Plus does not
- 3-day free trial on every eligible plan and interval
- Monthly plans add three $1 cycles after the trial; yearly plans go straight to the regular price
- One offer per merchant email; changing plans during the offer ends it
Troubleshooting
I don't see a free trial offered on my store.
The offer is only shown when Lulu is running it for new signups and your plan is paid by card through the standard billing flow. Stores outside Basic, Grow, and Advanced, stores billed another way, and email addresses that have already used the offer never see it.
Could I sign up again with a slightly different email to get a second trial?
No — eligibility is checked against a normalized form of your email (lowercase, with +tags and, for Gmail, dots removed), so a minor variation of the same address is still recognized as the same merchant.
What happens the moment my trial ends?
On a monthly plan, you move automatically into the $1-per-cycle period for three cycles, then your plan's regular price. On a yearly plan, you're charged the regular yearly price as soon as the 3-day trial ends.
I changed plans during my trial — did I lose the offer?
Yes. Upgrading or downgrading while the trial or the discounted cycles are still running ends the offer; the plan-change confirmation shows this and what you'll be charged before you confirm, so you can back out first.
Use the admin on a phone or tablet
Lulu has no separate mobile app — the same admin at your store's address adapts to small screens in any browser.
Illustrated guide: lulu.us.com/help/use-the-admin-on-mobile
Before you startThere's no Lulu app to install. Use your phone or tablet's normal browser (Safari, Chrome, etc.) and sign in exactly as you would on a computer.
1. Open your admin in a mobile browser
Go to your admin address (for example admin.lulu.us.com, or your store address followed by /admin, which forwards you there) and sign in as usual — the same login works on any device.
2. Open the menu
On screens 1024px wide or narrower, the sidebar collapses behind a menu button at the top left. Tap it to open the full navigation as a slide-in panel; tap the backdrop or the close button (or press Escape) to dismiss it.
3. Search the same way
Tap the search icon in the top bar — it collapses to an icon on very narrow phones — to look up pages, products, orders, or customers, exactly as on desktop.
4. Work with wide content
Tables and tab strips that don't fit your screen scroll sideways inside their own box, so the page itself never gets wider than your phone's screen.
5. Expect everything else to work
Orders, products, settings, and Go live all render and save the same way as on a computer — only the layout adapts to the smaller screen.
Completion checklist
- No app to install — use your phone or tablet's browser
- Sidebar becomes a hamburger menu below about 1024px wide
- Wide tables scroll inside themselves, not the whole page
Troubleshooting
Is there a Lulu app in the App Store or Google Play?
No. Lulu's admin is a responsive website, not a native app — there's nothing to download or install; you always use it through a browser.
The page looks squeezed or overlapping on my phone.
Make sure you're using an up-to-date mobile browser at normal zoom. The layout is tuned down to very narrow phones (around 360–390px wide), but an older browser or heavy zoom can still crowd the top bar.
Can my staff rely on mobile for daily work?
It's fine for checking orders, approving products, or a quick settings change. For heavy catalog work or theme editing, a larger screen is easier to work with.
Set up percentage, amount, Buy X Get Y, and free shipping discounts
Choose the right discount method and type, set eligibility, limits, schedule, and whether it combines with other discounts.
Illustrated guide: lulu.us.com/help/discount-types-bogo-free-shipping
Before you startDecide whether the discount should require a code or apply automatically.
1. Start a discount
Go to Discounts and click Create discount, then pick a type: Amount off products, Buy X get Y, Amount off order, or Free shipping.
2. Choose code or automatic
Under Method, choose Discount code (the customer types the code at checkout) or Automatic discount (applies on its own when the cart qualifies). For a code, write your own or click Generate random code; codes are saved in capital letters. For an automatic discount, enter a Title instead — customers see it in their cart and at checkout.
3. Set the value
For Amount off products or Amount off order, choose Percentage or Fixed amount and enter the value; for Amount off products, also choose what it Applies to: All products, Specific collections, or Specific products. For Buy X get Y, set Customer buys (a minimum quantity of items or a minimum purchase amount, from all products, chosen products, or chosen collections) and Customer gets (a quantity from chosen products or collections, at a discounted value: Percentage, Amount off each, or Free). A Free shipping discount has no value to set.
4. Set eligibility
Under Customer eligibility, choose All customers, Specific customer segments, or Specific customers. Be aware of how this is enforced today: a code limited to specific customers is refused at checkout for anyone else, but a segment limit is not yet checked at online checkout, so anyone who has the code can use it. An automatic discount limited to segments or customers is not applied automatically in the cart — use a code for customer-specific offers.
5. Set minimum purchase requirements
Under Minimum purchase requirements, choose No minimum requirements, Minimum purchase amount, or Minimum quantity of items.
6. Set maximum discount uses
Under Maximum discount uses, tick Limit number of times this discount can be used in total and enter a number, and/or tick Limit to one use per customer.
7. Limit where it works
Optionally use the Sales channels and Markets cards to limit the discount to certain sales channels and markets. Free shipping discounts also have Countries and Shipping rates cards, and Buy X get Y has Set a maximum number of uses per order. For a code, the Shareable link card gives you a link that applies it for the shopper once the discount is saved.
8. Set combinations
Under Combinations ("This discount can be combined with"), tick Product discounts, Order discounts, and/or Shipping discounts. All three are unticked by default, so a new discount can't be used alongside another one until you allow it.
9. Set active dates and save
Under Active dates, set a Start date and, if it's time-limited, tick Set end date and choose the end date. Check the Summary panel on the right, then save. Test with a qualifying cart and a non-qualifying one before sharing it. To pause a saved discount later, untick Discount is active, or select several discounts in the list and use Activate / Deactivate.
Completion checklist
- Picked the right discount category for the offer
- Set code vs. automatic correctly
- Set a minimum requirement if intended
- Set usage limits to control cost
- Decided what it can combine with
- Set a start date, and an end date if it's time-limited
Troubleshooting
Two discounts didn't stack at checkout even though I expected them to.
Combining is off by default for every pairing. Open each discount and tick the matching option under Combinations on both discounts — two discounts only stack when both allow it.
Can I generate 100 unique codes for one offer at once?
Not today — Lulu generates one code per discount, with a one-click random generator. For many unique codes, create separate discounts.
My Buy X Get Y discount gave the wrong item for free.
Check the Any items from choice on both Customer buys and Customer gets — a broad choice (for example a large collection) can let an unintended item qualify as the discounted item.
I limited a code to a customer segment, but other customers used it.
Segment limits are saved with the discount but aren't checked at online checkout yet. For a code that only certain people may use, choose Specific customers instead, which is enforced at checkout.
Limit a discount to certain sales channels and markets
Make a discount work only where you sell it: pick the sales channels and markets it applies to, and know what shoppers see when a code doesn't fit.
Illustrated guide: lulu.us.com/help/limit-a-discount-to-sales-channels-and-markets
Before you startThis works for every discount type, code or automatic. A discount with nothing chosen applies everywhere, exactly as it always has, so existing discounts are unchanged.
1. Open the discount
Go to Discounts and open an existing discount, or click Create discount and choose a type.
2. Choose the sales channels
In the Sales channels card, leave All sales channels selected, or choose Specific sales channels and tick the channels the discount may be used on: Online Store, Point of Sale, Facebook & Instagram, Google & YouTube, Marketplaces, AI shopping agents, or Headless (Storefront API). The names match the channels you publish products to.
3. Choose the markets
In the Markets card, leave All markets selected, or choose Specific markets and tick the markets (from Markets) the discount may be used in. Shoppers outside the ticked markets can't use it.
4. Know that Point of Sale and AI agents have no market
Point of Sale sales and carts built by AI shopping agents don't belong to a market. A discount limited to specific markets therefore never applies there. To make a discount work at the register, leave Markets on All markets and, if you like, limit it to Point of Sale under Sales channels.
5. Check the Summary and save
The Summary panel lists the channels and markets you chose. Save, then test with a cart on each channel or market you expect to work, and one you expect to be refused.
6. Know what shoppers see
If a shopper types a code that isn't valid on their channel, they see "This code can’t be used on this sales channel". If it isn't valid in their market, they see "This code isn’t available in your country or region". A code already in the cart that stops fitting (for example, after they enter a delivery address in another market) shows "Code … no longer applies" with a Remove link, and checkout refuses it before any payment is taken. An automatic discount that doesn't fit is simply skipped, with no message.
Completion checklist
- Chose the channels where the discount should work, or left All sales channels
- Chose the markets where it should work, or left All markets
- Did not limit to specific markets a discount you want to work at the register or for AI agents
- Tested a qualifying cart and a non-qualifying one
Troubleshooting
A market-limited code doesn't work at my register.
Point of Sale sales have no market, so a discount limited to specific markets never applies there. Set Markets to All markets and use Sales channels to control where it works.
A shopper says the code worked in the cart but not at checkout.
Markets are judged by the delivery country at checkout. If the delivery address is in a market you didn't tick, the code is refused with "This code isn’t available in your country or region" before payment.
A market I ticked shows as "Deleted market".
The market was removed after you saved the discount. It never matches anything; untick it and save.
Can I set this from the Markets page instead?
Not today. Under Markets → a market → Customizations, Discounts is not applied yet. Set channels and markets on the discount itself.
Limit a free shipping discount to countries and shipping rates
Offer free shipping only to chosen countries, and keep expensive shipping rates out of the offer by setting a maximum rate.
Illustrated guide: lulu.us.com/help/limit-free-shipping-by-country-and-rate
Before you startThese two cards appear only on Free shipping discounts. Handling fees are never waived by a free shipping discount.
1. Create or open a Free shipping discount
Go to Discounts, click Create discount, choose Free shipping, set the method and code or title, and set eligibility as usual.
2. Choose the countries
In the Countries card, leave All countries selected, or choose Selected countries, then use Add a country to pick each country from the list. Remove a country with the × next to its name.
3. Exclude expensive rates
In the Shipping rates card, tick Exclude shipping rates over a certain amount and enter the highest rate you want to cover, in your store currency. Rates above that amount keep their full price; a rate exactly equal to the amount is still free.
4. Review and save
Check the Summary panel, then save. Test with an address inside a chosen country and one outside it.
5. Know what happens outside your countries
The code isn't refused for a delivery country that isn't on the list. It stays applied, but nothing is waived there, so the shopper pays the normal rate. On the cart page, before a delivery address is entered, a country-limited offer can't know where the parcel is going, so shipping isn't shown as free until an address is entered.
Completion checklist
- Listed the countries that get free shipping, or left All countries
- Set a maximum rate if some shipping rates should stay paid
- Tested an address inside a listed country and one outside it
Troubleshooting
A shopper entered the code but still pays for shipping.
Check the delivery country is on your Countries list and that the chosen rate isn't above the amount in Shipping rates. Outside the list, or above the cap, the code stays applied but waives nothing.
My rate is exactly the maximum amount and it was free. Is that right?
Yes. Only rates above the amount are excluded.
Why isn't a country-limited code showing free shipping in the cart?
The cart page has no delivery address yet. Free shipping appears once the shopper enters an address at checkout.
Does it waive handling fees too?
No. Handling is never waived by a free shipping discount.
Can I include the rest of the world as one option?
Not today. Choose All countries, or list the countries you want.
Set a maximum number of uses per order on a Buy X get Y discount
Decide whether a Buy X get Y offer can repeat inside one order, and cap how many times it applies.
Illustrated guide: lulu.us.com/help/set-a-maximum-number-of-uses-per-order-on-buy-x-get-y
Before you startOne use is one full set of "Customer buys" items plus the "Customer gets" items. Discounts saved before this option existed keep working as one use per order.
1. Open the discount
Go to Discounts and open a Buy X get Y discount, or create one and fill in Customer buys and Customer gets.
2. Choose how often it repeats
Below Customer gets, leave Set a maximum number of uses per order unticked to let the offer apply as many times as the cart qualifies (buy 4, get 2 free when the cart has enough items). Or tick it and enter the highest number of uses, from 1 to 1000.
3. Check the Summary
The Summary panel shows either "Up to N uses per order" or "No limit on uses per order".
4. Know how repeats are counted
The cheapest eligible Customer gets items are discounted first. A further use needs another full set of Customer buys items (or another full purchase amount) still in the cart after the discounted items are taken.
5. Know what happens to existing discounts
Buy X get Y discounts you created earlier open with the box ticked and the number set to 1, which is how they always behaved. Untick it to let them repeat.
Completion checklist
- Decided whether the offer should repeat in one order
- Entered a number if you want to cap it
- Tested with a cart that has enough items for two uses
Troubleshooting
My Buy X get Y only applied once even though the cart had enough items.
Open the discount and check Set a maximum number of uses per order. Older discounts are set to 1; untick it for no limit, or raise the number.
Does this limit how many orders can use the discount?
No. It limits uses inside one order. Use Maximum discount uses for total or per-customer limits.
The number box shows a message.
Enter a whole number from 1 to 1000.
Share a discount link that applies the code for the shopper
Copy a link for a discount code and send it by email, social media or message. Shoppers who open it get the code applied to their cart automatically.
Illustrated guide: lulu.us.com/help/share-a-discount-link
Before you startThe Shareable link card appears on a saved discount that uses a code, on a store with its own online storefront. It isn't shown for automatic discounts or before you save.
1. Save the discount first
Create the discount code and save it. Then open it from Discounts.
2. Find the Shareable link card
In the right-hand column, the Shareable link card shows the link, made from your store's address, /discount/ and the code.
3. Choose where shoppers land
Under Send shoppers to, type a page on your store, such as /collections/sale. Leave it blank to send them to the home page. Only pages on your own store work; anything else sends the shopper to the home page.
4. Copy and share
Click Copy link and paste it into your email, ad or social post. If your browser blocks copying, select the text in the field and copy it by hand.
5. Know what the shopper experiences
The code is remembered in the shopper's browser for 14 days. It is applied to their cart as soon as it is valid for that cart. For example, once there is something in the cart, the minimum purchase is met, or the start date has arrived. If the cart already has a code that works, the link never replaces it. A code that doesn't exist, has expired, is used up, or isn't valid on the shopper's channel or market is ignored silently, with no error message. If your online store is password-protected, shoppers enter the password first.
Completion checklist
- Saved the discount before copying the link
- Set Send shoppers to if you want a specific page
- Tested the link in a private browser window with an item in the cart
Troubleshooting
I can't see the Shareable link card.
It only shows for a saved discount code, not an automatic discount, and only when your store has its own storefront address.
A shopper opened the link but sees no discount.
The code applies only when it is valid for their cart. Check the minimum purchase, dates, usage limits, sales channel and market. The link doesn't replace a code they already applied.
Can I link to a product or collection?
Yes. Type its path under Send shoppers to, for example /collections/sale.
Does the link follow the shopper across devices?
No. It is remembered in that browser only, not on the customer's account.
Set up a points-based loyalty program with tiers
Reward repeat customers with points on every paid order, let them redeem points for discount codes or catalog rewards, and reward your best customers with Silver and Gold tiers.
Illustrated guide: lulu.us.com/help/loyalty-points-program-tiers
Before you startThe points program itself is built in. The Rewards catalog needs the LoyalLane Rewards app (gift card rewards and subscription-renewal bonus points need its Growth plan), and the public /rewards page needs LoyalLane on the Starter plan or higher.
1. Open Loyalty
Go to Growth → Loyalty.
2. Turn on the program
Under Points program, switch the program on (it's off by default) and save. While it's off, customers don't earn or redeem points and the account-page widget stays hidden. Points are awarded when an order is paid and taken back proportionally on refunds.
3. Set the earn rate
Under Earning, set Points per [currency] spent — points earned for every unit of your currency spent, counted on the order subtotal after discounts (default 1). Optionally, under Frequency bonus, switch on Reward repeat orders and set Every Nth order and Bonus points (default: 200 points every 5th order).
4. Set up tiers
Under Tiers, set Min points (12 mo) and Earn multiplier for Silver and Gold (defaults: 1,000 points at 1.25× and 5,000 points at 1.5×). Bronze is the base tier at 1×. Gold's threshold must be higher than Silver's, and its multiplier can't be lower; multipliers go up to 10×.
5. Set redemption value
Under Redemption, set Points per 1 [currency] of discount (default 100) and Minimum points to redeem (default 500). The minimum must be a multiple of the points-per-unit rate.
6. Know how redemption works
When a customer redeems points for money off, they get a single-use discount code for them only, valid for about 6 months. If you have LoyalLane Rewards, you can also add up to 20 Rewards (Amount off, Percentage off, Free shipping, or Gift card, each with a points cost); a reward discount becomes a single-use code valid for 30 days, and a gift card is emailed to the customer and follows your gift card expiry setting.
7. Review members
Scroll to Members to see each customer's tier, points balance, lifetime points, and last activity. Use Adjust on a member to add or remove points with a reason; a removal can't take a balance below zero.
8. Check the account-page widget
Visit a customer account page on your storefront to confirm the loyalty widget shows their balance and tier once the program is on.
Troubleshooting
A customer's tier didn't update after a big order.
Tier is based on points earned in the trailing 12 months and is recalculated as soon as an order is paid (and after refunds or manual adjustments). Check that the order is marked paid, not just placed. Note that the tier multiplier on an order uses the customer's tier from before that order.
Can I give a customer bonus points manually?
Yes — in Members, click Adjust next to the customer, enter the points (negative to remove) and a reason. Manual points count toward the customer's tier and add to your points liability, so only adjust with a specific reason.
Create and send a marketing email campaign
Compose a branded email with a heading, button, and up to four products, choose an audience, send a test, and schedule it.
Illustrated guide: lulu.us.com/help/send-marketing-email-campaign
Before you startCampaigns go only to customers who accept email marketing. Sending through the platform's mail counts against your plan's monthly email allowance, shown at the top of the Email campaigns page; if you send through your own email provider account, the allowance doesn't apply.
1. Start a campaign
Go to Growth → Email campaigns, click Create email campaign, enter a Name, and click Create.
2. Write the content
Set the Subject (shown in the inbox) and Preview text (shown next to the subject in most inboxes), then a Heading and the Body.
3. Add a button and products
Optionally add a Button with a Label and Link, up to 4 Products (search and add them), and a Footer note.
4. Choose the audience
Under Audience → Send to, choose All subscribers or A segment, then pick the segment. The page shows how many subscribers match. Email campaigns can only use segments built from subscription status, number of orders, amount spent, or country — if a segment uses any other filter, a warning appears and the campaign can't be sent to it.
5. Link a tracking campaign (optional)
Optionally choose a Tracking campaign. Sessions carrying that campaign's UTM tags are attributed to it in Growth → Campaigns.
6. Preview and send a test
Check the Preview pane, then click Send test and enter up to 3 addresses (separated by commas or new lines) to see it in a real inbox.
7. Schedule or send
Click Send now, or click Schedule and choose Send at — at least a few minutes ahead and no more than 90 days out. Only a draft can be edited: once a campaign is scheduled, you can Cancel it but not change it. You can also Cancel a campaign while it's sending.
8. Review the report
After sending, open the campaign to see its Report — Recipients, Accepted, Failed, Skipped, Unsubscribed, and Attributed sessions — and the Recipients list with each address's status. Accepted means the mail provider took the message, not that it was delivered or opened.
Troubleshooting
My segment shows a warning in the Audience section.
Email campaigns can only target segments built from subscription status, number of orders, amount spent, or country. Edit the segment to use only those filters, or choose a different one.
Can I edit a campaign after scheduling it?
No — only drafts can be edited. Cancel the scheduled campaign, then create a new one with your changes.
Run marketing automations: abandoned checkout, order follow-up, and welcome emails
Run on-demand email jobs over your last 7 days of activity, and see each run's result.
Illustrated guide: lulu.us.com/help/run-marketing-automations
1. Open Automations
Go to Growth → Automations to see the flow catalog.
2. Know the three built-in flows
Abandoned checkout reminder emails every un-recovered abandoned checkout from the last 7 days with a link back to their cart. Order follow-up thank you emails a thank-you to customers whose orders were placed in the last 7 days. Welcome new subscribers emails customers who joined in the last 7 days and accept email marketing. Each run handles up to 200 recipients.
3. Run a flow
Click Run automation on the flow you want. Each run is a one-off batch job over your store's current data, sent right away — not a standing, always-on trigger. Email delivery must be set up for your store, otherwise the run is refused.
4. Check the last run
Each flow card shows Last run with a summary such as "3 emails sent (3 matched)", or Never run.
5. Review flow runs
Scroll to Flow runs to see past runs and search them.
6. Know when a flow is replaced
If you've installed the Postbox Email & SMS app, its automatic workflows replace all three flows (abandoned checkout, post-purchase, and welcome). The flow cards then show "Postbox now sends this automatically." with an Open Postbox workflows button instead of Run automation.
Troubleshooting
I expected these to run automatically every day.
These three flows don't — each is a batch job you run yourself over the last 7 days. For automatic abandoned-checkout emails, turn on Settings → Checkout → Abandoned checkout emails. For automatic welcome, post-purchase and abandoned-checkout emails, install Postbox Email & SMS.
Will running "Order follow-up thank you" twice in a day email customers twice?
Yes. Each run emails every customer with an order in the last 7 days, whether or not they've had the email before, so repeated runs send duplicates. The same applies to the manual abandoned-checkout reminder. Leave at least a week between runs.
Does the manual abandoned-checkout reminder respect my 'Email subscribers only' setting?
No. The manual run emails every un-recovered abandoned checkout from the last 7 days. The Send to and delay choices in Settings → Checkout apply only to the automatic emails.
Recover abandoned checkouts: reminder emails and settings
Turn on automatic reminder emails for incomplete checkouts, choose who gets them and how soon, and measure what's actually recovered.
Illustrated guide: lulu.us.com/help/abandoned-checkout-recovery-settings
1. Review incomplete checkouts
Go to Orders → Abandoned checkouts to see captured checkouts with the email, items, subtotal, last activity, and whether each is Abandoned or Recovered.
2. Open the recovery setting
Go to Settings → Checkout and find the Abandoned checkout emails card.
3. Turn it on
Tick Send abandoned checkout emails automatically. It's off by default.
4. Choose who gets them
Under Send to, pick Anyone who abandons checkout, or Email subscribers who abandon checkout (the default — only customers who accept email marketing).
5. Choose the delay
Under Send email, pick 1 hour, 6 hours, 10 hours (marked Recommended, and the default), or 24 hours after abandonment.
6. Save
Click Save on the card. Lulu checks about every 15 minutes, so an email can arrive a little after the delay. Once on, any un-recovered checkout from the last 7 days that is past the delay is emailed — including ones abandoned shortly before you turned it on. Each abandonment gets one email; a shopper who abandons again later can get a new one.
7. Measure recovery honestly
Use the Recovered status in Orders → Abandoned checkouts and compare against actual Orders, not the number of reminders sent — a sent reminder isn't a completed sale.
Troubleshooting
Should I email everyone or only subscribers?
Emailing everyone recovers more sales but can reach people who never opted into marketing email; emailing only subscribers is the safer default for compliance-sensitive stores.
Is there a difference between this and the "Abandoned checkout reminder" automation in Growth → Automations?
Yes. This setting sends automatically, once per abandonment, at the delay you choose. The Growth → Automations flow is a manual batch job that emails every un-recovered checkout from the last 7 days each time you run it, ignoring the Send to and delay choices — so running it while automatic emails are on can email shoppers twice.
I installed Postbox — will shoppers get two reminders?
No. When the Postbox abandoned-checkout workflow is on, it replaces these automatic emails.
Turn review photos and referrals into discount coupons
Email a coupon to customers who leave a review (especially with a photo or video), and reward customers who refer a friend who buys.
Illustrated guide: lulu.us.com/help/review-coupons-and-referrals
Before you startRequires the Judge Product Reviews app on its Growth plan or higher. Without it, the Coupons & referrals tab offers a link to the App Store.
1. Open Reviews
Go to Reviews and open the Coupons & referrals tab. It shows Coupons issued, Friends referred, Waiting on refund window, and Referrers rewarded.
2. Turn on review coupons
Under Review coupon, switch on Email a coupon when a review is approved. It's off by default, since it gives a discount away automatically.
3. Choose the trigger
Under Which reviews earn it, choose Reviews with an approved photo or video (the default) or Any approved review. Each review earns at most one coupon, even if you approve it again.
4. Set the coupon value
Choose Percentage or Fixed amount under Discount and enter the value (default 10%). Each coupon is a single-use code for that customer only, expires after 30 days, and is listed in Discounts.
5. Set up referral rewards
Under Referrals, switch on Add a referral link to the review thank-you email (off by default). Set the Friend's discount (a code for the friend's first order) and the Reviewer's reward, each as a percentage or a fixed amount.
6. Set the refund window and cap
Set Refund window (days) — how long a friend's paid order must stay un-refunded before the reviewer's reward is issued (1–90, default 14) — and Friends per reviewer, the most friends one reviewer can refer (1–100, default 20).
7. Know the guardrails
Only reviews written on your storefront earn rewards — imported reviews never issue a coupon or referral link. A friend order that is refunded (fully or partly), voided, or cancelled never earns a reward. Self-referrals, friends who already have an order with you, and friends who were already referred are refused.
Troubleshooting
A customer says they didn't get their review coupon.
Confirm the review was written on your storefront (not imported), was approved, matches the trigger you chose (any review vs. photo/video only), and that review coupons were switched on before it was approved.
Can a referral reward be issued twice for the same friend?
No — each friend can be referred only once, and the reviewer's reward for that friend is issued at most once, after the refund window passes.
Markets: currency, catalogs, and per-market settings
Give a market its own currency — priced from a catalog, converted live, or converted at a rate you set — and understand which per-market settings change what shoppers see today and which are saved for a future update.
Illustrated guide: lulu.us.com/help/market-currency-price-rounding
Before you startYou need the store owner account or a staff account allowed to manage settings. A market can convert prices on its own; a catalog-priced market also needs a price list in its currency (Customers → Companies → Price lists).
1. Open or create a market
Go to Markets and open a market, or click Create market. Under Market details, set the Name and Status (Draft or Active), and under Includes click Add condition to choose the countries/regions it covers. Click Save in the bar at the top.
2. Review Customized vs. Inherited
The market page lists Customized settings (overridden for this market) and Inherited settings (taken from your Store default market, the parent of every market).
3. Choose the market's currency and how it's priced
Click the + next to Currency under Inherited (or the pencil next to it under Customized). Choose a Currency, then under Price conversion pick one of three ways to price it: Fixed prices from a catalog, Automatic exchange rate, or Manual exchange rate. A live preview at the bottom of the popover shows a sample price converted with your choices before you save.
- Fixed prices from a catalog
- Automatic exchange rate
- Manual exchange rate
4. Fixed prices from a catalog
Prices come from a price list in the market's currency, attached under Markets → Catalogs (see the next step). Any variant that isn't in the list is converted at your store's daily exchange rate instead, rounded to the nearest 10 minor units. With no price list attached in a convertible currency, the market only relabels and still charges your store currency.
5. Automatic exchange rate
Every product price is converted using a live exchange rate that refreshes about once an hour, with no price list required. If a currency's rate suddenly jumps by more than 10%, Lulu holds the old rate for a few hours rather than price the change immediately — in case it's a bad reading, not a real move. If no live rate is available yet (for example, right after a restart), the market falls back to its fixed-catalog pricing until one arrives, and the market page shows a warning.
6. Manual exchange rate
Enter your own rate as "1 [your store currency] = [this many of the market's currency]". It must be greater than 0 and have at most 6 decimal places. Prices update as soon as you save — there's no live lookup to wait for.
7. Set price rounding
For Automatic or Manual conversion, choose a Price rounding rule: Don't round (nearest cent), Round up to .99, Round up to .95, Round up to .00 (whole unit), or Round to the nearest whole unit. It's applied to converted product prices only — shipping rates, handling, discount amounts and tax are converted but never rounded this way, and a fixed catalog price from a price list is never rounded (only its FX-fallback prices are).
8. Know the currency limit
Automatic and Manual conversion only work into two-decimal currencies. A currency with no decimals (like JPY or KRW) or three decimals (like KWD or BHD) can only be priced from a catalog — the popover greys out the other two options and explains why.
9. Attach a price list for catalog pricing
Go to Markets → Catalogs and choose a price list for the market. This is what makes Fixed prices from a catalog actually price the market in its own currency; Automatic and Manual conversion don't need one. A price list in your store currency instead applies its percentage or fixed price adjustment on top of the conversion.
10. Save and understand the price a shopper is quoted
Click Done, then Save. A shopper's price (and exchange rate) is held for up to 2 hours once they start checking out, so it can't change under them mid-payment. If it genuinely changes — you edited the rate, or the live rate moved — before they pay, they see a message that prices were updated and are asked to review the new total and pay again; they're never charged for the old total.
11. Know what the other customizations do today
Customizing Discounts, Theme, Domain or Checkout on a market is saved and listed under Customized, but none of them change what shoppers see yet; they will be applied in a future update. Taxes and Returns, covered in the next two steps, already do apply.
12. Override taxes for a market
Click the + next to Taxes under Inherited (or the pencil under Customized) to set a Rate %, whether prices include tax, and whether tax applies to shipping for this market — leave a field blank to keep your store's Settings → Taxes value for it. This override applies at checkout using the market serving the shopper's SHIPPING address, not necessarily the market they're browsing in (a pickup or digital-only order, which has no delivery address, uses the browsing market instead). It's locked in the moment they pay: if the override changes — by you, or because a live rate moved — before they finish, they see a message that prices were updated and are asked to review and pay again, never charged under stale numbers. The order remembers the tax settings it was placed under, so editing the override later never changes an existing order's total.
13. Override return rules for a market
Click the + next to Returns under Inherited (or the pencil under Customized) to set a return window, a restocking fee percentage, and final-sale collections for this market alone — leave a field blank to fall back to Settings → Policies → Return and cancellation rules. This override decides what a customer sees and is allowed to do the moment they request a return on an order placed in this market: the return window, which collections are excluded as final sale, and the restocking fee shown to them and to you on the order's Return requested card.
14. Revert a customization
Click the − next to a Customized setting to return it to Inherited, then Save.
15. Test the market
Preview your storefront with an address or country inside the market's regions and run a test checkout to confirm the prices, rounding and currency shoppers see and pay.
Completion checklist
- Picked Fixed prices from a catalog, Automatic, or Manual exchange rate for the market's currency
- Attached a price list under Markets → Catalogs if you chose Fixed prices from a catalog
- Set a price rounding rule if you chose Automatic or Manual — it doesn't apply to a catalog's fixed prices
- Confirmed the currency is two-decimal if you want Automatic or Manual conversion
- Tested a checkout in the market's region to see the real converted, rounded total
- Set a Taxes and/or Returns override only on markets that genuinely need different rates, inclusion, or return rules than your store default
Troubleshooting
I set a currency on my market but shoppers still see my store currency.
Check the Price conversion mode. Automatic and Manual convert every price without needing a price list — if shoppers still see your store currency with one of those chosen, check for a warning banner in the Currency popover (for example, no live rate is available yet). Fixed prices from a catalog only works once a price list in that currency is attached under Markets → Catalogs; without one, the market keeps charging your store currency.
My price rounding choice isn't changing the price I see.
Price rounding only applies to Automatic or Manual conversion, not to a fixed price from a price list — set the exact price you want directly in the price list for those. Also check the preview in the Currency popover reflects your saved choice, not an unsaved draft.
A shopper says their total changed partway through paying.
Lulu locks the exchange rate a shopper is quoted for up to 2 hours so it can't move mid-payment. If it still changed — usually because the rate moved or you edited it while they were checking out — they're shown the new total and asked to pay again; nothing is ever charged at the old, stale total.
I can only pick "Fixed prices from a catalog" for one of my markets.
That market's currency has zero or three decimal places (for example JPY, KRW, KWD, BHD). Automatic and Manual conversion only support two-decimal currencies, so those options are disabled for it.
I customized Domain (or Theme, Checkout) for a market and nothing changed.
Those three customizations (plus Discounts) are recorded for a future update and don't change the storefront yet. Domains are managed under Settings → Domains. Taxes and Returns overrides, on the other hand, apply immediately to orders placed in that market — if you expected one of THOSE to change something, check you saved the popover and that the order's shipping country is actually served by this market.
Which market's tax settings apply to an order?
The market serving the order's SHIPPING address decides tax, not necessarily the market the shopper was browsing in. A pickup or digital-only order, which has no delivery address, uses the browsing (session) market instead. Once an order is placed, it keeps the tax settings it was quoted under, even if you edit the market's override afterwards.
A customer's return didn't follow my market's Returns override.
Lulu uses the market an order actually belongs to — recorded at checkout — falling back to the active market serving its shipping country, then your Store default, if that's unknown. A blank field in a market's Returns override falls back to your store-wide Settings → Policies rules, not to zero.
Publish languages and translate your store with Wise AI
Choose which languages customers can browse your storefront in, and use Wise AI to translate product content into each one.
Illustrated guide: lulu.us.com/help/translate-store-languages-wise-ai
Before you startTranslating with Wise AI uses one AI credit per language each time you click Translate.
1. Open Languages
Go to Settings → Languages.
2. Know your default
English is your store's default language. It is always published and shows as English (Default) – Published at the top of the language table.
3. Publish additional languages
Under Published languages, tick each language you want customers to be able to view your online store in.
4. Save
Click Save. Each ticked language now shows as Published in the table and can be chosen on your storefront.
5. Translate a product
Open a saved product in the product editor and find the Translations card. Pick a language tab and click Translate to have Wise AI fill in the translated title, description, SEO title and meta description. You can also type translations yourself.
6. Review AI translations
Read through the generated translation and correct anything that's off, especially sizing, legal or safety text, then save the product. The translation isn't stored until you save.
7. Translate product stories (optional)
If you use product content stories, their editor has its own translate option for the languages you've published.
Troubleshooting
A language is published but the storefront still shows English.
Publishing a language only makes it selectable; it doesn't translate anything by itself. Open the product's Translations card, translate (or type) the content for that language, and save the product. Content without a translation is shown in English.
Can I unpublish a language without losing its translations?
Unchecking a language in Settings → Languages stops it from being offered to customers, but doesn't delete the translated content already saved — recheck it later to make it available again.
The Translate button isn't there.
Save the product first; new, unsaved products show "Save the product first to translate". Also make sure you've published at least one language besides English in Settings → Languages.
Schedule market and price-list changes with Rollouts
Stage a set of market and price-list changes — a sale's pricing, a market going live, a currency, tax or return override — and apply them immediately or at a scheduled time.
Illustrated guide: lulu.us.com/help/schedule-market-changes-with-rollouts
Before you startYou need the same settings access as Markets. Rollouts change markets and price lists that already exist in your store; it doesn't create new ones.
1. Open Rollouts
Go to Markets → Rollouts to see every rollout for this store, newest first, with a status filter (Draft, Scheduled, Applied, Canceled).
2. Create a rollout
Click Create rollout, give it a name, and add changes as setting keys and values — for example a market's status, its currency, catalogs, taxes or returns customization, or a price list's adjustment type or value.
- markets.<id>.status — "active" or "draft"
- markets.<id>.customizations.<currency|catalogs|taxes|returns> — the same values the market editor accepts, or null to revert it
- price_lists.<id>.adjust_type — "percent" or "fixed"
- price_lists.<id>.adjust_value — a whole number (basis points for percent, cents for fixed)
3. Review before applying
Each change is validated with the same rules as the Markets and Catalogs editors — an invalid value, or an id that isn't one of this store's own markets or price lists, is refused with a specific error next to that change, and nothing in the rollout applies until every change in it is valid.
4. Apply now, or schedule it
Choose Apply now to write every change immediately, or set a Schedule time to apply it automatically later. A scheduled rollout applies itself within about a minute of that time — you don't need to be signed in when it runs.
5. See what each change replaces
Once applied, the rollout's detail view shows "was …" with the previous value next to each change, so you can see exactly what it replaced.
6. Handle a schedule-or-cancel conflict
If a scheduled rollout already applied by the time you try to reschedule or cancel it, Lulu refuses the request and shows its real current status instead of silently overwriting it — reload the rollout and decide from there.
7. Know the retry behavior
If an automatic apply fails, Lulu retries it up to 3 times before giving up and recording the error on the rollout.
Completion checklist
- Used setting keys the rollout understands (market status, market currency/catalogs/taxes/returns, or a price list's adjustment type/value)
- Reviewed every change for an error before applying
- Chosen Apply now for an immediate change, or set a Schedule time for later
- Checked back after a scheduled time passed to confirm it actually applied
Troubleshooting
My rollout shows an error instead of applying.
Each change key is validated before anything is written — an unsupported key, an invalid value, or an id that doesn't belong to one of this store's markets or price lists is listed as an error next to that change, and nothing in the rollout applies until every change is valid.
Can two rollouts touch the same market at once?
Yes, but each apply writes on top of the market's current saved values in its own transaction, so whichever one commits last wins for any setting they both changed — check the market's Customized settings afterwards if you're running overlapping rollouts.
I tried to cancel a scheduled rollout but got an error.
That means it already applied in the background before your cancel reached the server — Lulu refuses rather than silently ignore it, and shows the rollout's real current status (Applied) instead.
SEO & AI: control crawlers, llms.txt, and search appearance
Manage who can find your store — search engines and AI answer engines — and set the title, description, and social image people see when they do.
Illustrated guide: lulu.us.com/help/seo-ai-search-appearance
Before you startHave your store's home page title, a one-sentence description, and (optional) a social preview image ready (1200 x 628 px is recommended). You need the store owner account or a staff account allowed to manage settings.
1. Open SEO & AI
Go to Online Store → SEO & AI. The page is split into Search engines, AI & answer engines (GEO), llms.txt, robots.txt, and Search appearance.
2. Control search engine indexing
Under Search engines, turn Search engine indexing on or off and click Save. New stores start with indexing turned off. While it is off, robots.txt blocks all crawlers and every page carries a noindex header; while it is on, your store serves a public sitemap.xml and search engines can crawl and index every page.
3. Choose which AI crawlers can read your store
Under AI & answer engines (GEO), turn on AI crawlers & answer engines to let AI bots fetch your pages and /llms.txt (new stores start with this off). Once it is on, each known AI bot is listed under AI search / live retrieval or Model training with its own switch, so you can let assistants answer live questions about your store while blocking your content from model training. Click Save.
4. Check your llms.txt
The llms.txt card previews the plain-text guide to your key pages, collections, and policies written for language models, with a View live /llms.txt button. Only policies you have actually written are linked (an empty one is left out), and your Contact information policy is added as a Contact section. It is only published while AI crawlers are turned on and at least one AI channel is on under Sales channels → Agentic.
5. Review robots.txt
The robots.txt card is a read-only preview of the exact file your store serves to crawlers. It refreshes after every save, so it always reflects the indexing and crawler choices you just made. It also includes the AI channels you switched off under Sales channels → Agentic: their crawlers are disallowed there even though their switches on this page stay on.
6. Set your search appearance
Under Search appearance, enter the Home page title (up to 70 characters) and Meta description (up to 320 characters) shown in search results and link previews, then click Save. Click Add image to upload a social sharing image; it is saved as soon as the upload finishes. A preview card shows how the result will look.
7. Test it
Search your store name in a private browser window, and share your home page link in a chat app to preview the social card.
Completion checklist
- Decided whether search engines should index the store yet
- Chosen which AI crawlers are allowed
- Set a home page title and meta description
- Added a social-sharing image
Troubleshooting
Why doesn't my store show up in Google yet?
Check that Search engine indexing is turned on (new stores start with it off) and that the store isn't still password-protected. After that, search engines can take days to weeks to crawl and index a new store.
Blocking an AI crawler removed me from an AI assistant's answers. Why?
Live-retrieval bots (the ones assistants such as ChatGPT or Perplexity use to fetch the web) and model-training bots have separate switches. Blocking a live-retrieval bot, or turning AI crawlers off entirely, stops those assistants from reading and citing your store. Blocking only training bots does not.
Where does llms.txt live?
At /llms.txt on your store's own domain. It only serves content while AI crawlers are turned on in SEO & AI and at least one AI channel is on under Sales channels → Agentic.
Find and fix SEO issues at scale: SEO health and the bulk editor
Audit your active products for missing SEO titles, meta descriptions, alt text, thin descriptions and duplicate titles, then fix many at once with the WiseSEO bulk SEO editor.
Illustrated guide: lulu.us.com/help/fix-seo-issues-seo-health-bulk-editor
Before you startHave products already created. SEO health is available to every store. The Bulk SEO editor is part of the WiseSEO app, so install WiseSEO from the App Store before using the export/import steps.
1. Open SEO health
Go to Online Store → SEO health. It scans your active products (up to 500) and the top tiles count SEO title issues, Meta description issues, Missing alt text, Thin descriptions, and Duplicate SEO titles. Click a tile to filter the list to that issue.
2. Filter by issue type
Use the filter tabs (All issues, SEO title, Meta description, Alt text, Thin description, Duplicate title) to work through one issue type at a time.
3. Fix a product directly
Click a flagged product in the list to open it in the product editor, fix its SEO title, meta description, description, or image alt text, then save.
4. Export many products for bulk editing
Go to Online Store → Bulk SEO editor (shown once WiseSEO is installed) and click Export CSV under 1. Export. The file lists your products, collections, pages, and blog posts with their handle, title, SEO title, meta description, and image alt text.
5. Edit and re-import
Edit the SEO title, meta description, image alt text, or handle columns in a spreadsheet, keeping the type and id columns unchanged, because rows are matched by them. Then, under 2. Import, click Add file (or drag the CSV in). Up to 10,000 rows can be imported at a time. Changing a handle automatically creates a redirect so the old URL keeps working.
6. Review the preview and apply
Before anything is saved, a preview shows how many rows were read and will change, plus any errors and warnings, and a table with the Type, Handle, Title, and Changed fields of each changed row. Click Apply to save the changes, or Cancel to discard them. Rows with errors are skipped.
7. Re-check SEO health
Return to SEO health and confirm the issue counts dropped.
Completion checklist
- Reviewed each issue tile at least once
- Exported a fresh CSV before making bulk edits
- Checked the import preview's changed fields and warnings before clicking Apply
Troubleshooting
What counts as a "thin description"?
SEO health flags any active product whose description is under 200 characters as a thin description. That is usually too short for search engines to understand the product well.
My bulk import didn't change anything.
Check the preview: rows whose values match what is already saved are not counted as changes, and rows with errors (for example an unknown id or an invalid handle) are skipped. Also make sure you clicked Apply after reviewing the preview.
Some cells were ignored with a warning.
Blog posts don't have their own SEO title or meta description yet, and only products store image alt text (on the first image). Changes to those cells are reported as warnings and left unapplied.
I don't see Bulk SEO editor in the menu.
The bulk editor comes with the WiseSEO app. Install WiseSEO from the App Store and the menu item appears under Online Store.
Customize your password page
Change the heading, message, background image, logo, and button text visitors see on your store's password ("Opening soon") page.
Illustrated guide: lulu.us.com/help/customize-your-password-page
Before you startThe password page is only shown while your store is in development mode and password protection is on with a password set (Online Store → Preferences → Password protection).
1. Turn on password protection
Go to Online Store → Preferences → Password protection, turn on Enable password, enter a password, optionally write a Message to your visitors, and click Save.
2. Open your theme editor
Go to Online Store → Themes and click Customize on your live theme (or Edit theme on a draft theme).
3. Switch to the Password template
In the theme editor's page picker at the top, choose Password. Then select Password page in the section list to open its settings.
4. Set the heading and message
Change the Heading (blank shows "Opening soon") and the Message. A blank message uses the Message to your visitors you set under Preferences.
5. Add a background and logo
Upload a Background image and a Logo. Leaving the background blank uses a default photo; leaving the logo blank shows your store name as text.
6. Relabel the form
Change the Password field label and Button label if you want wording other than "Enter store password" and "Enter".
7. Save and preview
Save the theme, then open your storefront in a private/incognito browser window to see the password page as a first-time visitor would. Changes on a draft theme only show to visitors once that theme is published.
Troubleshooting
I changed the password page but still see the old one.
Visitors see the password page settings of your live theme. Save (and publish, if you edited a draft), then reload the storefront in a new private window. A browser that already entered the password, or that used your preview link, skips the page entirely.
Can I remove the password page entirely?
Yes. Turn off Enable password under Online Store → Preferences, or launch the store to production. The theme editor's Password page settings only matter while password protection is on.
Preferences: URL redirects, spam protection, and crawler signatures
Forward old links to new ones with 301 redirects, and review the automatic redirection, spam protection, and crawler access settings.
Illustrated guide: lulu.us.com/help/preferences-redirects-spam-crawler-access
Before you startYou need the store owner account or a staff account allowed to manage settings.
1. Open Preferences
Go to Online Store → Preferences.
2. Add a URL redirect
Under URL redirects, enter the old path in Redirect from (must start with / and contain no spaces, e.g. /old-product) and the destination in Redirect to (a path starting with / or a full https:// URL), then click Add redirect. The redirect is saved immediately and works as a 301 (permanent) redirect.
3. Mind the limit
The list shows how many of your 500 redirects you've used. Click Delete on ones you no longer need to make room.
4. Automatic redirection
Under Automatic redirection, switch on Country/region and/or Language, then click Save. With Country/region on, a first-time visitor whose location is served by a different active market is switched into it automatically — once per visit, and never for a visitor who already picked a market themselves (they see the prompt in the next step instead). With Language on, a visitor is switched once per visit into the best-matching published language from their browser's language setting, when it differs from what they're seeing. Redirection never applies to search engines or other known crawlers, and never fires on the checkout, account, password, or theme-editor pages. Language alternates (hreflang) are already added automatically for languages you publish, whatever these switches are set to.
5. See the prompt shoppers get instead
When a redirection switch is off, or a visitor already chose a market or language that differs from where they appear to be, they see a small dismissible prompt instead of being switched automatically: "It looks like you're visiting from {country}. Shop in {market}?" with Yes and No thanks. Yes switches them over through the normal ?market= / ?lang= flow; No thanks (or closing it) is remembered on that browser for 30 days.
6. Spam protection
Under Spam protection, "Enable on contact and newsletter signup forms" and "Enable on login, create account and password recovery (storefront and marketplace)" control which forms show a captcha challenge; a hidden bot-trap field is always active on those forms regardless of these switches. Choose a Captcha provider — Off (bot trap only), Cloudflare Turnstile, or hCaptcha — then enter the Site key and Secret key that provider issued you. A provider chosen without both keys shows a "misconfigured" warning, and the protected forms refuse every submission with "Please try again" until you add the keys or set Captcha back to Off, so a store is never silently left unprotected. Leaving both fields blank lets Lulu fall back to its own shared keys for that provider while you set up your own. Switching provider needs a new secret key — a secret saved for one provider isn't reused for the other. Click Save.
7. Record a crawler signature
Under Crawler access, click Create signature and enter the domain of the tool that will crawl your store. A Signature, Signature-Input, and Signature-Agent value is created, valid for 90 days. Note: your storefront does not yet check signed requests, so a signature does not currently grant a crawler any extra access. Use SEO & AI to allow or block crawlers today.
8. Manage existing signatures
Use the All / Active / Expired tabs to review signatures, Copy one again, or Revoke one you no longer need.
Completion checklist
- Decided whether automatic country/region and language redirection should be on, knowing visitors who already chose get the prompt instead of a silent switch
- Picked a Captcha provider and entered both its Site key and Secret key if you want more than the built-in bot trap
- Re-entered the secret key after switching Captcha provider, since a saved secret isn't shared between providers
Troubleshooting
A redirect isn't working.
Confirm the Redirect from path starts with /, has no spaces, and matches the old URL path exactly (without the domain). Duplicate redirect-from paths and a redirect that points to itself are rejected when you add them.
Does a crawler signature let a tool past my password page or SEO & AI blocks?
No, not yet. Signatures are recorded for your reference, but the storefront doesn't check them yet. Crawler access is controlled today by the switches in Online Store → SEO & AI.
I turned on Captcha but visitors say forms are refusing everything.
That's the fail-closed behavior: a provider chosen without both a site key and secret key counts as misconfigured, and every protected form answers "Please try again" rather than go unprotected. Add both keys — or leave both blank to use Lulu's shared keys for that provider — or set Captcha back to Off.
Does the automatic country or language switch ever fire twice, or loop?
No — it's limited to one automatic switch per visit, is skipped for search engines and other known crawlers, and never fires on the checkout, account, password or theme-editor pages.
Find orders with filters, search, and sales channel
Narrow the order list by payment status, fulfillment status, sales channel (including POS), date, and free-text search, with your filters kept in the URL.
Illustrated guide: lulu.us.com/help/find-and-filter-orders
Before you startOpen Orders. You need permission to view orders. Draft orders live on their own page under Orders → Drafts.
1. Open the order list and its tabs
Orders opens to a list showing order number, date, customer, channel, total, payment status, fulfillment status, delivery status and item count. Tabs across the top give quick views: All, Unfulfilled, Unpaid, On hold, and Open (not cancelled and still owing a shipment or a payment).
2. Filter by payment and fulfillment status
Use the Payment filter (Pending, Partially paid, Paid, Partially refunded, Refunded, Voided) and the Fulfillment filter (Unfulfilled, Partially fulfilled, Fulfilled) to narrow the list — for example, orders that are paid but unfulfilled.
3. Filter by sales channel, including POS
Use the Channel filter to isolate orders by where they came from: Online Store, Point of Sale (Lulu's own register), External POS (sales sent in from your own in-store POS system), Draft order, Agentic, Facebook, Google, Amazon, eBay, or Etsy.
- Online Store
- Point of Sale
- External POS
- Draft order
- Agentic
- Facebook
- Google
- Amazon
- eBay
- Etsy
4. Search and set a date range
Use the search box for an order number, customer name, or email, and the From/To date fields to bound a range — useful before exporting or reconciling a period. Dates use your store's time zone.
5. Sort and page through results
Click the Order, Date or Total column header to sort. The tab, filters, search, sort and page number are kept in the page address, so a bookmarked or shared link reopens the same view.
6. Know what "archived" means
If "Automatically archive the order" is on in Settings → General → Order processing (it is on by default), an order that is paid and fulfilled — or fully refunded — is tagged "archived". It stays in the list and in search; the Open tab already leaves out paid, fulfilled orders.
Completion checklist
- The Channel filter is how you isolate POS and connected-channel sales from Online Store orders.
- Filters, search, sort, and page number all live in the page address — safe to bookmark or share.
- Archived orders are tagged "archived", not hidden or deleted.
Troubleshooting
An order I know exists isn't showing up.
Clear the Payment, Fulfillment, and Channel filters first — a narrow combination of filters is the most common reason an existing order disappears from the list. Also check the date range.
I can't tell which orders came from my physical POS versus my own checkout.
Use the Channel filter: "Point of Sale" is Lulu's own register; "External POS" is a sale sent in from your own connected in-store POS system.
Read an order's details page and use its timeline
Understand each card on a single order — status badges, Accept order, holds, the staff-only timeline, notes and tags — and how to move between orders.
Illustrated guide: lulu.us.com/help/order-details-and-timeline
Before you startOpen Orders and click an order. Anyone who can view orders can read this page. Accepting orders and posting comments need "Manage order information"; holds and fulfilling need "Fulfill and ship" (both are in the built-in Staff role). Cancelling, refunding, marking as paid and marking as delivered need their own permissions, which Administrators have.
1. Read the header
The page header shows the order number with its payment and fulfillment status badges (and a Pickup badge for pickup orders), Prev/Next arrows, and a More actions menu with Print packing slip, Print invoice and Cancel order. Cancel order is only enabled while the order is completely unfulfilled. A cancelled order shows a banner with the cancellation date and reason.
2. Accept the order and set an expected delivery date
The first card is Accept order. Enter an Expected delivery date and choose Accept order; the date is shown to the customer on their order status page and in the shipping email as the estimated delivery. After acceptance the card reads Accepted with the time, and the button becomes Save date so you can update the expected date later.
3. Put the order on hold when something is wrong
The fulfillment hold card offers Mark as on hold while anything is left to fulfil. Pick a reason — Awaiting payment, Awaiting return items, High risk of fraud, Incorrect address, Inventory out of stock, Unknown delivery date, or Other — add optional notes, and optionally hold only specific lines. While a hold is active, Fulfill items is disabled ("Release the hold before fulfilling") and the order moves from the Unfulfilled tab to On hold; Release hold reopens it.
4. Use the Timeline for staff-only comments
The Timeline card lists the events on the order — acceptance, holds, fulfillments, payments, refunds, cancellation, note and tag changes, and comments — each with its time. Type in "Leave a comment..." and choose Post (or press Enter) to add an internal comment of up to 5,000 characters. As the card says, only you and other staff can see comments.
5. Add a note and tags
The right column has a Notes card (one note per order, up to 5,000 characters, edited with the pencil icon) and a Tags card. Select Save to keep your changes; each change is also logged on the timeline. Notes and tags are for your team — they aren't shown on the storefront.
6. Check the Customer card
Customer shows the linked customer profile (click through to it), contact information, and the Shipping address — or the Pickup location for a pickup order. The Billing address appears only when the order has no shipping address (for example, a gift-card-only order). Guest orders show the contact details without a profile link.
7. Mark it delivered when the parcel arrives
Once an order has a shipment, a delivery card shows "On its way" or "Delivered". If you turned on Automatic tracking in Settings → Shipping (with your own 17track or AfterShip key), Lulu checks shipments about every 20 minutes and can mark orders delivered for you; "Refresh tracking" checks now. Otherwise, choose Mark as delivered yourself — it updates the customer's order status page and sends them the delivered email.
8. Move to the next or previous order
Use the Prev/Next arrows in the header to step through orders by order number (newest first) without going back to Orders.
Completion checklist
- New orders are accepted with a realistic expected delivery date before you start packing.
- Problems are recorded as a hold with a reason, so fulfillment is actually blocked.
- Shipped orders are marked delivered — automatically with Automatic tracking, or by hand.
Troubleshooting
Cancel order is greyed out in More actions.
Cancel order is only available while the order is completely unfulfilled — and a paid order must be fully refunded before it can be cancelled. Once anything has shipped, use a refund instead — see Refund, cancel, and restock an order.
Fulfill items is disabled even though stock is available.
The order is on hold — the help text under the button says "Release the hold before fulfilling." Open the hold card, review the reason, and choose Release hold.
Can the customer see my timeline comment or the order note?
Timeline comments and tags are internal and never shown to the customer. Only the expected delivery date, shipment and tracking details, and the delivered confirmation reach the customer, through emails and their order status page.
The order still says "shipped" days after the carrier delivered it.
Without automatic tracking, the status doesn't change by itself. Turn on Automatic tracking in Settings → Shipping, or choose Mark as delivered on the order; that also sends the customer the delivered email.
Mark an order as paid, or collect a deposit balance
Record payment manually on a pending order, capture or void an authorized card payment, and understand the separate balance-due flow used for deposits and pay-later terms.
Illustrated guide: lulu.us.com/help/collect-payment-and-mark-as-paid
Before you startOpen the order. You need the "Record payments" permission. Mark as paid only appears while the order's payment status is Pending and it isn't cancelled.
1. Confirm the order is actually pending
Check the payment-status badge at the top of the Payment card — Mark as paid only shows for an order whose financial status is pending.
2. Choose Mark as paid
Choose Mark as paid. The confirmation shows the amount and warns that this can't be undone — confirm only after you've actually received the money outside checkout (for example, a bank transfer or cash). It records the payment; it doesn't charge anyone.
3. An authorized card payment works differently
When a card payment through Stripe was only authorized (held) rather than captured at checkout — see "Capture payments later" — the order's payment status is Authorized, and Mark as paid is refused with "This payment is authorized — capture it instead of marking it as paid." Use the Capture payment and Void buttons on the order page instead: Capture payment charges the card (in full or for a smaller amount, releasing the rest of the hold), and Void releases the hold without charging it.
4. Know when Mark as paid is unavailable
If the payment for an order is handled somewhere else — for example, collected by a marketplace — the button doesn't appear and a banner on the payment card explains why. Reconcile through whoever collected the payment instead.
5. A deposit or pay-later order works differently
An order that used a deposit or pay-later term shows a separate card with Payment received, Balance due and the due date. From it you can choose Collect payment (emails the customer a link to pay the balance from their order status page), Mark as paid (when you collected the balance yourself), or Edit due date.
6. After marking as paid
Depending on your Order processing setting, marking an order as paid can also auto-fulfill and/or auto-archive it immediately — check the order's updated statuses rather than assuming nothing else changed.
Completion checklist
- Only use Mark as paid once money has actually arrived — it's a record, not a charge.
- A missing Mark as paid button usually means the payment method doesn't allow recording payment locally.
- Marking as paid can trigger auto-fulfill/auto-archive depending on your store's processing settings.
- An Authorized order needs Capture payment (or Void) — Mark as paid is refused on it.
Troubleshooting
The Mark as paid button isn't on the order.
It only shows for a pending, non-canceled order whose payment method allows recording payment locally. Check the banner text on the Payment card, which explains the specific reason when it's hidden.
I marked an order as paid by mistake.
Marking as paid can't be undone. If no money was actually received, record a refund for the amount and add a timeline comment explaining what happened — see Refund, cancel, and restock an order.
Mark as paid gave an error about the payment being authorized.
That order's card was only authorized, not yet charged. Capture it (in full or in part) from the Capture payment button on the order page, or Void it to release the hold — see "Capture payments later".
Fulfill orders, add tracking, and choose a carrier
Ship some or all of an order's items, pick a carrier from the built-in list, add a tracking number, and control whether the customer is emailed.
Illustrated guide: lulu.us.com/help/fulfill-orders-tracking-and-carriers
Before you startOpen the order. The unfulfilled-items card with the fulfill form appears while at least one item is left to fulfil and the order isn't cancelled (pickup orders use the Pickup card instead). If the order is on hold, the form shows but Fulfill items stays disabled until you release the hold.
1. Choose the quantity to fulfill per item
Each unfulfilled line shows a quantity field defaulting to its full remaining quantity — reduce it to ship only part of that line, for a partial fulfillment.
2. Pick a carrier
Choose a Shipping carrier from the list: None, USPS, UPS, FedEx, DHL Express, Royal Mail, Canada Post, Australia Post, Aramex, Sri Lanka Post, Pronto Lanka, Domex, Koombiyo Delivery, Fardar Express, or Other.
- USPS
- UPS
- FedEx
- DHL Express
- Royal Mail
- Canada Post
- Australia Post
- Aramex
- Sri Lanka Post
- Pronto Lanka
- Domex
- Koombiyo Delivery
- Fardar Express
- Other
3. Add a tracking number (and URL if needed)
Enter the Tracking number (optional). The Tracking URL is optional too — leave it blank and it is worked out from the carrier and number, so you usually only need the number.
4. Decide whether to notify the customer
"Send shipment details to the customer" is checked by default, including when you ship without a tracking number — uncheck it if you specifically don't want a shipping-confirmation email sent for this fulfillment.
5. Choose Fulfill items
Choose Fulfill items to create the shipment. The order then shows it as a fulfilled card with the carrier, tracking link, items and date.
6. Repeat for the rest, as separate shipments
If items ship at different times, fulfil the remaining quantities later as additional, separate shipments — each with its own carrier, tracking number and notify choice. Each shipment is listed on the order with its tracking link, and with a Delivered date once delivered.
Completion checklist
- Reduce a line's quantity before fulfilling to ship it partially; fulfill the remainder later as a second shipment.
- Leave Tracking URL blank to let Lulu build it from the carrier and number automatically.
- Uncheck the notify box only when you deliberately don't want a shipping email sent for that shipment.
Troubleshooting
The Fulfill items button is disabled.
Check that at least one item has a quantity greater than zero selected, and that the order isn't currently on hold (a fulfillment hold blocks fulfilling until it's released).
My tracking link opens the wrong page.
The auto-detected URL is built from the carrier you chose plus the number — if your shipment used a different actual carrier than selected, fix the carrier choice or enter the correct Tracking URL directly.
A customer says they never got a shipping email.
Check whether "Send shipment details to the customer" was unchecked on that specific fulfillment, and confirm the order has a valid email address.
Fulfill a local-pickup order: ready, then picked up
Walk a local-pickup order through its two hand-over steps instead of the ship/tracking flow, and choose when to notify the customer.
Illustrated guide: lulu.us.com/help/local-pickup-fulfillment
Before you startOpen an order placed with local pickup as its delivery method. The order page shows a Pickup card instead of the ordinary fulfill form.
1. Check the pickup location
The Pickup card shows which location the customer chose, with its address and its "ready in" time.
2. Mark the order ready for pickup
Once the order is actually ready at that location, choose "Mark as ready for pickup." This is available while the order isn't canceled or on hold and is still awaiting that step.
3. Choose whether to notify the customer
The "Send the customer an email" checkbox (on by default, and only shown when the order has an email address) controls whether the customer is emailed when you mark the order ready or picked up.
4. Mark the order picked up
When the customer collects it, choose "Mark as picked up" and confirm. This is available any time before the order is marked picked up, as long as it isn't cancelled or on hold.
5. Track the pickup status
The card's status moves from awaiting, to ready, to picked up, with times for when it became ready and when it was collected.
Completion checklist
- Local-pickup orders use Ready → Picked up instead of carrier/tracking fulfillment.
- The notify checkbox only appears when the order actually has an email address to send to.
- Both ready and picked-up timestamps are recorded on the order for your own reference.
Troubleshooting
I don't see a Pickup card on this order.
The Pickup card only replaces the normal fulfill form for orders placed with local pickup as the delivery method — a shipped order uses the carrier/tracking flow described in the fulfillment article instead.
Can I mark an order picked up without marking it ready first?
Yes — "Mark as picked up" is available whenever the order isn't already picked up (and isn't on hold or cancelled), so you can skip the ready step if the customer collects straight away. Marking it ready first lets you tell them it's waiting.
Refund, cancel, and restock an order
Record a refund with or without restocking, understand how money actually moves for each payment method, and know how cancelling differs from refunding.
Illustrated guide: lulu.us.com/help/returns-refunds-and-restock
Before you startOpen the order. Refund appears on the payment card while the order is paid, partially paid or partially refunded and has an amount left to refund. Cancel order is in the More actions menu.
1. Know when to use a formal return instead
When a customer requests a return from their order status page, or when you want to track received items and fees against a specific return, use the order's Returns card and the full return workflow instead of an ad hoc refund — see manage-returns. The steps below are for refunding or cancelling an order directly, without creating a return object.
2. Open Refund and choose what to return
Choose Refund. Enter the quantity being refunded for each item, a reason (visible only to staff), and the refund amount — the form shows how much is available to refund, and supports partial as well as full refunds.
3. Decide whether to restock
Check "Restock items" to add the refunded quantities back to inventory. This checkbox is unavailable on an order that's already canceled — stock for a canceled order was already handled at cancellation time, so refunding it again will not restock a second time.
4. Know how the money moves
A card payment through Stripe, or a PayPal payment, is refunded straight through that provider when you choose Refund — the customer's card or PayPal balance is credited automatically. Cash, bank transfer, pay at the store, the Sri Lankan gateways (PayHere, Onepay, WebXPay, PAYable, Mintpay, KOKO), Marx and Point of Sale tenders can't be refunded through an API, so the form tells you "Return manually" and shows a notice such as "Refund recorded — return [amount] to the customer by cash." for you to act on yourself.
5. Choose whether to notify the customer
Tick or untick "Send a notification to the customer" before confirming. It's on by default. The email explains that the refund is on its way through the original payment method, or — for a manual return — that you'll return the money directly, and shows the amount in your store's currency either way.
6. Record a refund you already made outside Lulu
If you already refunded the customer in your Stripe or PayPal dashboard, tick "Record a refund made outside Lulu" instead of sending the refund again. Lulu records it on the order without contacting the provider. If the order has more than one charge, pick which payment it was refunded on.
7. Confirm and check the result
Choose Refund to confirm. The order's Refunded line and Net payment update, its payment status changes to Partially refunded or Refunded, and the refund appears on the timeline. A card or PayPal refund that the provider hasn't confirmed yet shows as still processing — see the next step.
8. If a refund is still being processed
While a refund is waiting on an answer from the provider, the order page shows a blocked message and you can't start a new refund on that order — choose "Retry reconciliation" to check with the provider again and finish it. The same order can't be returned at the Point of Sale register either, including as an exchange that pays money out, until that refund is resolved.
9. Cancel an order instead, when appropriate
Use More actions → Cancel order for an unfulfilled order that shouldn't go ahead. Choose a reason and decide whether to "Restock inventory"; the customer is emailed that the order was cancelled. A paid order must be fully refunded first — cancelling is refused until nothing is left to refund. A deposit on a pre-order isn't refunded automatically when you cancel; refund it separately.
10. Remember there's no online "exchange" action
There is still no single "exchange" action for an online order — refund the returned item (with or without restock), then create a new order or draft order for the replacement. Exchanges remain available only at the Point of Sale register. Unlike before, an order's items CAN now be edited after it's placed (adding, removing, or changing quantities) — see edit-an-order — but that's a separate action from refunding or exchanging.
Completion checklist
- Card and PayPal refunds are sent to the provider automatically — cash, bank, pay at the store, local gateways and POS tenders need you to return the money yourself.
- Restock on refund and restock on cancel are separate choices at separate moments.
- An open refund blocks any new refund, and any POS return that pays money out, until it's reconciled.
- A Return requested card shows what a customer's self-serve request already excluded and what fee to deduct, pulled from your return rules or a market override — it's a reminder, not an automatic charge.
- There's still no single exchange action for online orders — use a refund plus a new order. Order items CAN now be edited after the sale (see edit-an-order), separately from refunding.
Troubleshooting
I refunded a canceled order and expected stock to come back, but it didn't.
That's expected — stock was already handled when the order was canceled, so the Restock checkbox is disabled on a canceled order's refund to avoid double-restocking the same units.
A customer's return request shows a restocking fee — does Lulu charge it automatically?
If you're processing it as a formal return (see manage-returns), the return's own Refund panel deducts the restocking and return-shipping fee from the suggested amount automatically on the first refund of that return — you can still change the amount before confirming. If you're refunding directly from the order's Refund button instead, Lulu never deducts a fee on its own; enter the amount you want to charge.
The refund amount doesn't match what I expected.
The refund amount is whatever you enter, up to the "available for refund" figure shown under the field. Check whether you meant to include shipping or handling, and remember earlier partial refunds reduce what is available.
The order says a refund is still being processed and won't let me refund again.
That means Lulu hasn't had a definite answer back from the card or PayPal provider yet for an earlier refund on this order. Choose "Retry reconciliation" on the order page to check with the provider and finish it before starting a new refund or taking a return at the register.
I already refunded the customer in my Stripe or PayPal dashboard — won't this refund them twice?
Use "Record a refund made outside Lulu" on the Refund form instead of a normal refund. It records what you already did without sending anything to the provider again. If you try an ordinary refund after refunding outside Lulu, Lulu detects the provider is already ahead of its own records and asks you to record it this way first.
A customer wants a different size instead of a refund.
There's no built-in online exchange action: refund the original item (deciding whether to restock it) and create a new order or draft order for the replacement size.
Print a packing slip or invoice for an order
Generate a print-ready packing slip or invoice from any order page, and switch between the two formats without leaving the document.
Illustrated guide: lulu.us.com/help/print-packing-slips-and-invoices
Before you startOpen the order and use the More actions menu.
1. Open the print view
In the order's More actions menu, choose Print packing slip or Print invoice. The document opens in a new tab, formatted for printing, with a "Back to order" link.
2. Check which document you're viewing
The document names itself — Packing slip or Invoice — and shows the store name, order number and date. A packing slip's address section is headed "Ship to"; an invoice's is headed "Billed to" and also shows the payment status. Either shows "Cancelled" if the order was cancelled.
3. Switch between packing slip and invoice
Use the alternate-document link in the top bar ("Invoice" while viewing a packing slip, or "Packing slip" while viewing an invoice) to flip formats without going back to the order first.
4. Print
Choose Print to open your browser's print dialog. The top bar and back link don't appear on the printed page or in a saved PDF.
Completion checklist
- Packing slip and invoice are two views of the same print page — switch with the top-bar link rather than navigating back and forth.
- The store name, order number, and placed-on date appear on both documents automatically.
- The print bar itself never appears in the printed output.
Troubleshooting
The address section is blank on my printed document.
This shows "No address on this order" when the order genuinely has none recorded — check the order's shipping/billing address was captured at checkout.
I need a PDF, not a paper printout.
Use your browser's print dialog's "Save as PDF" destination instead of a physical printer — the page is the same either way.
Help a customer with a digital download
Find where a customer sees their download, re-send access, and know what a refund or cancellation does to it.
Illustrated guide: lulu.us.com/help/help-a-customer-with-digital-downloads
Before you startOpen the order in Orders. The product needs a digital file attached (Products → the product → Digital files) for any of this to apply — an order with no digital lines shows no Digital downloads card.
1. Open the order’s Digital downloads card
Open the order in Orders. If it has a digital line, a Digital downloads card lists each file with its download count and limit, last download time, expiry, and a state badge (Available, Awaiting payment, Revoked, Expired, Limit reached).
2. Point the customer to their copy
A paid order’s confirmation email has a “Your downloads” section, and the customer’s order status page (linked from their account’s order history, or the link in their confirmation email) shows the same files with a Download button while available. Staff never see the actual download link — only the customer’s email and order page carry it.
3. Reset a download count
If a customer used up their download limit legitimately (for example, reinstalling on a new device), open the file’s row and choose Reset count to give them the same limit again.
4. Extend access past its expiry
A file past its Link expires after date can’t be downloaded. There’s no separate “extend” action — use Restore if it was revoked, or have the merchant add the file again and grant it to that order’s past purchase if it needs a fresh expiry window.
5. Revoke access
Select Revoke on a file’s row to cut off a customer’s access immediately, for example after a goodwill refund processed outside the normal refund flow.
6. Know what a refund or cancellation already does
Cancelling the order, fully refunding it, voiding it, or fully refunding that line in Lulu’s admin all revoke digital access automatically — you only need to use Revoke for a case the automatic rule doesn’t cover, such as a partial refund processed directly at your payment provider.
Completion checklist
- You checked the order’s Digital downloads card before telling a customer their access is fine (or isn’t).
- A download-limit reset or access revoke was applied to the right file on the right order.
- You know a provider-side partial refund doesn’t revoke access by itself — refund the line in Lulu instead, or revoke it by hand.
Troubleshooting
A customer says they never got their download email.
Check the order’s financial status first — an unpaid order gets no download links at all. If it’s paid, point them to their order status page instead (same files, same Download buttons), and check your email deliverability if confirmation emails are going missing generally.
A customer paid by bank transfer and says there’s no download link in their confirmation.
That’s expected — an order that isn’t paid yet at checkout gets no links in its first confirmation email. Once you mark it as paid, a separate “Your downloads are ready” email goes out with the links.
I refunded the order at Stripe directly, not in Lulu — did the download get revoked?
A full refund processed at the provider is detected and revokes access once the webhook arrives. A partial refund at the provider does not revoke access on its own — refund the specific line in Lulu’s admin, or revoke the file by hand on the order’s Digital downloads card.
Can I see the actual download link to send it to a customer myself?
No — the admin order page never shows the link itself, only the file, its state, and usage. Direct the customer to their confirmation email or order status page, or use Reset count / Restore if their access needs fixing.
Download your digital purchases
For shoppers: find your download links after paying for a digital product, and understand download limits and link expiry.
Illustrated guide: lulu.us.com/help/download-your-digital-purchases
Before you startYour order needs to be paid — download links are only ever sent or shown for a paid order, and the store needs to have attached a file to what you bought.
1. Check your confirmation email
Once your order is paid, look for a “Your downloads” section in your order confirmation email, listing each file with its size. If you paid by a method that settles after checkout (like bank transfer), you’ll instead get a separate “Your downloads are ready” email once the store marks your order as paid.
2. Or open your order status page
Open the link in your confirmation email, or sign in and find the order under your account’s order history. A “Your downloads” card lists the same files, each with a Download button while it’s available.
3. Open a download link
Clicking a download link or button first opens a short page showing the file name, size, and downloads left, with its own Download button — select that to actually start the file downloading. Only pressing this second Download button counts toward your limit; simply opening the link or having an email app preview it does not.
4. Watch your downloads-left count
If the file has a download limit, the page shows how many downloads you have left out of the total. Buying more than one copy gives you that many times the limit (for example, 2 copies of a 3-download file give you 6 downloads).
5. Know when a link stops working
A download stops working if the store set it to expire after a number of days (counted from when you paid) and that time has passed, if you’ve used up its download limit, or if your order is refunded or cancelled. The page tells you which of these applies.
6. Ask the store for help
If you need more downloads, a fresh link after it expired, or your access was revoked in error, contact the store you bought from — they can reset your download count or restore your access from their order page.
Completion checklist
- You checked both your confirmation email and your order status page if you can’t find a download.
- You know your download count only goes down when you press Download on the file’s own page, not when you open the email link.
Troubleshooting
I paid, but I don’t see any download link.
If you paid by a method that doesn’t settle instantly (such as a bank transfer), your links appear only once the store confirms your payment — watch for a “Your downloads are ready” email, or check your order status page.
The page says my download is no longer available for this order.
This means the order was refunded or cancelled, which automatically ends access to its downloads. Contact the store if you believe this is a mistake.
The page says my download link has expired, or I’ve reached my download limit.
Contact the store you bought from — they can reset your count or give you a fresh window from their side; there’s nothing to change on your end.
Does opening the link in my email count as a download?
No — opening or previewing the email link only shows you an informational page. Only pressing the Download button on that page counts toward your limit, so forwarding or previewing the email is always safe.
Manage returns
Create a return for items a customer is sending back, approve or decline a customer's own return request, receive items, and refund through the return.
Illustrated guide: lulu.us.com/help/manage-returns
Before you startOpen the order. The Returns card lists any returns already started, and offers Create return when eligible items exist.
1. Open the order's Returns card
On the order page, the Returns card shows any returns on this order and, when items qualify, a Create return button.
2. Create a return
Click Create return. For each eligible item (only shipped items that aren't refunded and aren't already on another live return are listed), set a quantity and a reason. Optionally enter a Restocking fee and a Return shipping fee — both are deducted from the refund you issue later — and Return instructions for the customer. Decide whether to send the return-confirmation email, then click Create return.
3. Review a customer's own request
When a customer requests a return from their order status page (your store needs self-serve returns turned on — see your customer-account settings), it appears with status Requested and a Review request button.
4. Approve or decline
Open the return and either Approve return (optionally add Return instructions — where to send the items, how to pack them) or Decline (pick a reason: Final sale, Return period ended, or Other, with a message). The customer is emailed either way unless you turn it off.
5. Receive items
Once the return is open, use Receive items: enter how many of each line arrived, tick Restock for the ones going back into stock, choose the location to restock at, and decide whether to email the customer that their items arrived.
6. Refund through the return
Use Refund on the same return: choose how many units of each line to refund. The suggested amount is the units' value minus any restocking or return-shipping fee — fees are only deducted on the first refund of a return — capped at what's left to refund on the order. Enter a reason, decide whether to notify the customer, and confirm. Money moves exactly like the order's own Refund: automatically for Stripe and PayPal, or recorded for you to return manually for cash, bank transfer, and other manual payment methods.
7. Follow the return's status
Requested moves to Approved (shown as open) once you act on it, then to Returned (closed) once every line is both received and refunded — or to Declined or Canceled. Close, Reopen, and Cancel buttons appear on the return page when they apply; you can only cancel a return that hasn't received or refunded anything yet.
8. Never refund again while a refund is pending
If the payment provider does not confirm a refund straight away, or the provider refunded the money but your store could not record it, the return shows a banner: "A refund on this return is still being confirmed by the payment provider. Use "Retry reconciliation" on the order; it links here once it settles." While that banner is shown the return's Refund panel is not offered and the return cannot be cancelled. On the order page the refund is listed with a status such as Needs reconciliation or "Refunded — not recorded". Open the order and select Retry reconciliation; your store checks with the provider and records the refund, and no money is sent again. The return then links the refund automatically.
- Do not use the order's own Refund to repeat it: the money may already have left your account.
- If only part of the amount settled, the money is recorded on the return but no item line is marked refunded; check the amounts on the return.
9. Filter orders by return status
On the orders list, filter by Return status: Return requested, Return in progress, or Returned.
Completion checklist
- Create a return (or review a customer's request) before receiving or refunding anything
- Approve or decline a customer's request with a reason — they're emailed either way unless you turn it off
- Receive items and tick Restock for the ones going back into stock
- Refund through the return so its fee deductions and status update together
- Use Retry reconciliation on the order if a return's refund is pending, and never refund that return again by hand.
Troubleshooting
A return I created doesn't list the item I wanted.
Only shipped items that aren't already refunded or on another live return can be added to a new return — check the item hasn't already been refunded or returned.
The suggested refund is lower than the item's price.
Your restocking fee and/or return-shipping fee are deducted from the first refund of that return only — later refunds on the same return don't deduct them again.
I received items but they weren't restocked.
Check Restock was ticked for that line when you received it, and that the order isn't canceled — a canceled order's stock was already handled at cancellation, so receiving on it doesn't restock a second time.
Can I still use the order's regular Refund button for something that isn't a formal return?
Yes — use the order's own Refund for an ad hoc refund. Use the return's Refund panel when you want the fee deductions and the return's own status to move together.
The return shows a refund as pending, but the customer says they were already paid back.
Treat it as paid. A pending refund means the provider may already have moved the money. Do not refund again; open the order and select Retry reconciliation so the refund is recorded and linked to the return.
Edit an order after it's placed
Add a product, remove one, or change a quantity on an order that hasn't shipped yet, then collect the difference or refund it.
Illustrated guide: lulu.us.com/help/edit-an-order
Before you startOpen the order and click Edit. Editing is available while the order is unfulfilled, not canceled, has no card authorization still outstanding, and has no open refund attempt — see What can't be edited below.
1. Open the order and click Edit
The Edit page shows the order's current items on the left and a running Summary on the right.
2. Add a product
Search by name or SKU under Add product and click Add on the result you want — the line appears under Items marked Added, priced at the variant's current price converted to the order's currency.
3. Change or remove a quantity
Use the +/− stepper, or type a number, on an existing line. Setting it to 0 marks the line for removal (click Undo to bring it back). Gift cards, pre-order/selling-plan lines, auction wins, and custom designs can't have their quantity changed.
4. Add a discount to a newly added line
On an added line, click Add discount, choose Percentage or an amount off each unit, add a reason, and Apply. This only works on lines you've just added — the order's own order-level discount is never re-applied.
5. Enter a reason
Type a short note in Reason for edit — it's staff-only and shows on the order's timeline.
6. Read the Summary before updating
It shows the new subtotal, discount, tax, and total, and tells you what happens next: nothing collected yet, an amount to collect, or an amount to refund.
7. Click Update order
What happens depends on the order: an unpaid order's totals simply change. A paid order that still has a balance due grows or shrinks that balance, turning the order Partially paid so you can collect the new balance. A paid order with no balance due refunds the value of anything you removed first, then adds the value of anything you added as a new amount owed.
8. Collect or confirm the result
If money is now owed, use Collect payment on the order page (sends a payment-request email, or Mark as paid once it arrives). If money was refunded, the order's payment status updates (Partially refunded) and the refund appears on the timeline. The customer is emailed the before/after lines when Send the customer an order updated email is ticked.
9. Discard instead
Click Discard, or just navigate away (you'll be warned about unsaved changes), to cancel the edit without changing the order.
Completion checklist
- Add, remove, or change quantities, then read the Summary before you click Update order
- Know you can't change gift card, pre-order, auction, or custom-design lines
- Check whether the result is "nothing collected", "collect a balance", or "refund the difference"
- Use Collect payment or check the refund on the timeline after updating
Troubleshooting
There's no Edit button on this order.
The order is fulfilled, canceled, has an outstanding card authorization (capture or void it first), is a marketplace or external-POS order, or already has another edit in progress on it.
The balance due doesn't net against the refund when I remove one item and add another.
That's a known limitation — removing and adding on the same paid edit refunds the removed value and separately collects the added value, rather than netting them into one smaller balance.
The page says this order needs reconciliation.
An earlier edit's refund (for removed items) has not fully settled with the payment provider, or settled without being recorded. Select Retry on the edit page, or Retry reconciliation on the order page, once the provider confirms. No refund is sent a second time.
The price of an item I added doesn't match what the original order shows for it elsewhere.
Added lines price at the variant's CURRENT price, converted to the order's currency — not the price the customer originally paid when the order was first placed.
Update order says the refund for the removed items succeeded but the new items could not be added.
The removed items were already refunded and that refund will not be requested again. The edit page shows the settled amount and a Retry button; select Retry (or Retry reconciliation on the order page) to add the new items.
Review an order's fraud analysis
Read an order's risk level, what drove it, and the recommended action, so you can decide whether to fulfil, investigate, or cancel.
Illustrated guide: lulu.us.com/help/review-fraud-analysis
Before you startOpen the order page — the Fraud analysis card appears for any order placed after fraud analysis was turned on for your store.
1. Read the risk badge
The Fraud analysis card shows a Low, Medium, or High risk badge with a short meter.
2. Read the recommendation
Accept, Investigate, or Cancel, based on the score.
3. Check the indicators
A list explains what raised or lowered the risk — for example a failed card security code (CVC) check, a mismatched IP country, a first order much larger than your store's average, a throwaway email domain, or Stripe Radar's own verdict. Each is flagged as a risk, a safe/positive fact, or informational. Positive facts (card checks passed, a returning customer, a matching IP country) are listed too, even though they don't add to the score.
4. Act on it
Fulfil normally for a low-risk order you're comfortable with, hold and investigate a medium-risk one, or cancel a high-risk one you don't want to ship.
5. Re-run the analysis
Click Run analysis again to re-check — useful after you've looked into it yourself, or if new information has come in. A medium/high result, or any change in level, is recorded on the order's timeline.
6. Spot risky orders across your store
On the orders list, High risk and Medium risk chips appear next to flagged orders, and you can filter the list by Fraud risk.
7. See the bigger picture
Analytics > Reports > Fraud analysis shows orders by risk level, their share of sales, and how many cancelled orders were cancelled for fraud.
Completion checklist
- Read the badge, the recommendation, and the indicator list before acting
- Re-run the analysis after investigating, or after getting the Stripe webhook's own verdict
- Filter the orders list by Fraud risk to find flagged orders quickly
- Check Analytics > Reports > Fraud analysis for the store-wide picture
Troubleshooting
This order shows "hasn't been analysed".
It was placed before fraud analysis was turned on for your store, or wasn't paid by a method that's scored yet.
What makes a card payment score High automatically?
A Stripe Radar verdict of "highest" or "blocked" always forces High risk; a failed CVC check pushes the order to at least Medium on its own.
Can I see exactly why the IP-country flag fired?
The card shows the signal itself (for example "IP country doesn't match the shipping/billing country") but not the raw IP address. Cloudflare's own unknown-country codes are ignored so they never falsely trigger this flag.
No risk signals were found, but I still don't trust this order.
"No risk signals" only means nothing in Lulu's checks stood out — it's one signal among others, not a guarantee; use your own judgement alongside it.
Act on several orders at once
Select multiple orders on the orders list to mark them paid, fulfil, cancel, archive, tag, or print packing slips in one go.
Illustrated guide: lulu.us.com/help/bulk-actions-on-orders
Before you startGo to Orders. Tick the checkbox on each order you want to act on (up to 250 at a time) — the bulk action bar appears above the list once you've selected at least one.
1. Select orders
Tick the checkboxes on the orders list. The bulk action bar appears above the list.
2. Fulfil or mark as paid
Click Fulfill or Mark as paid directly in the bar. Each order is checked against the same rules as doing it one at a time.
3. Print packing slips
Click Print packing slips to open one printable page with a page break between each selected order's slip.
4. Open More actions for the rest
Click More actions for Archive orders, Unarchive orders, Add tags, Remove tags, or Cancel orders (shown in red).
5. Confirm the action
A dialog explains that orders that can't be processed are skipped and listed afterwards. For Add tags/Remove tags, type the tags separated by commas. For Cancel orders, choose a reason and whether to Restock inventory. For Fulfill, choose whether to send shipping confirmation emails.
6. Read the result
A banner reports how many succeeded, how many were skipped, and names every skipped order with the reason — for example "Only pending orders can be marked as paid."
7. Export instead
Click Export selected in the same bar to download a CSV of just the orders you ticked, instead of acting on them.
Completion checklist
- Select up to 250 orders at a time before choosing an action
- Read the result banner for exactly which orders were skipped, and why
- Use Export selected when you just need a CSV, not an action
Troubleshooting
Some orders in my selection didn't get fulfilled or marked paid.
Each order is checked against the same rule as doing it individually — for example, only a pending order can be marked paid. The result banner names which ones were skipped and the reason.
Can I buy shipping labels or capture payments in bulk?
Not yet — those still need to be done order by order.
Is there a saved "Archived" view?
Not yet. Archiving just adds the "archived" tag to an order — filter or search the orders list by that tag instead of a dedicated saved view.
Edit tracking and send shipping updates
Correct a fulfilment's carrier, tracking number or tracking link after shipping, and choose whether the customer gets a Shipping update email.
Illustrated guide: lulu.us.com/help/edit-tracking-and-shipping-updates
Before you startOpen the fulfilled order and find the fulfilment card (named like #1001-F1) whose tracking you need to correct. You need the Fulfill and ship permission. The Edit tracking button is not shown on cancelled orders.
1. Open Edit tracking
On the order page, find the fulfilment card and select Edit tracking. The Edit tracking window opens.
2. Change the carrier, number or link
Choose the Shipping carrier, edit the Tracking number and, if needed, the Tracking URL. Leave Tracking URL blank and it is worked out from the carrier and number ("Auto-detected from carrier + number if left blank").
3. Decide whether to notify the customer
Notify customer of the change is ticked by default. Untick it for a correction you do not want to email about.
4. Save tracking
Select Save tracking. The toast reads "Tracking updated and customer notified" or just "Tracking updated", and the fulfilment card shows the new carrier and number.
5. Know when the Shipping update email sends
The Shipping update email only goes out when the tracking number or carrier actually changed, and once per distinct value: saving the same number again does not send a second email, but a genuine second correction does.
6. Know that carriers can correct tracking too
If ShipStation or Shippo sends your store a replayed shipment with a corrected carrier or number, your store applies the new tracking to the same fulfilment and sends one Shipping update email, using the same once-per-value rule. Cancelled orders and shipments already delivered are not changed.
7. Turn the email on or off, or edit its wording
Go to Settings > Notifications, open Shipping updates > Shipping update (or Out for delivery), and use the Send this email checkbox, or edit the subject and HTML. See understand-the-shipping-emails and customize-notification-emails.
Completion checklist
- Correct the tracking on the fulfilment card with Edit tracking, not in an order note.
- Decide per correction whether to leave Notify customer of the change ticked.
- Remember a Shipping update email only sends when the number or carrier changed.
- Check Settings > Notifications if a shipping email is not being sent at all.
Troubleshooting
I corrected a typo in the tracking number but no email went out.
Check you actually changed the number or carrier (not just re-saved the same value), and that the Shipping update template isn't turned off in Settings > Notifications.
A customer got two shipping update emails for the same shipment.
That means the carrier or number genuinely changed twice — each distinct value only emails once, so a second email means a second real correction.
Can I preview or edit what the shipping update email says?
Yes — go to Settings > Notifications > Shipping update or Out for delivery; see customize-notification-emails.
Request a return from your order
Ask the store to accept a return on an eligible order, and track it from request to refund — if the store has turned this on.
Illustrated guide: lulu.us.com/help/request-a-return-as-a-customer
Before you startOpen your order from the link in your order confirmation or shipping email, or from your account if you're signed in.
1. Open your order
Use the link from your order confirmation or shipping email, or sign in and find the order in your account.
2. Check you can request one
A Request a return button only appears on an order that's fully or partly shipped and paid (or partly refunded), hasn't been cancelled, and is within the store's return window — and only if the store has turned self-serve returns on. If it's outside the window or the items are final sale, the page explains why instead of showing the button.
3. Submit the request
Click Request a return. Optionally explain why you're returning it, then click Submit return request.
4. Wait for the store to respond
You'll see "Return requested — the store will be in touch at [your email]."
5. Track the return
Once the store responds, a Returns section on your order page shows its status: Requested, Approved — send items back (with any instructions the store gave you), Declined (with the reason), or Returned — along with how many items were received and how much was refunded.
6. Get your refund
Once the store receives and refunds your items, the refund goes back to your original payment method; it's listed under your order's refunds.
Completion checklist
- Open your order using the link from your confirmation or shipping email
- Check the page for a Request a return button, or for why it's not eligible
- Watch the Returns section on your order page for status updates
Troubleshooting
There's no "Request a return" button on my order.
Either the store hasn't turned on self-serve returns (contact them directly), the order isn't eligible yet (for example, not shipped, or already cancelled), or it's outside the store's return window or marked final sale — the page explains which.
I already requested a return — can I ask again?
Not while that request is still open. If the store declines it, you can request again.
My return says "Approved" but I haven't heard how to send items back.
Check the instructions shown on your order page's Returns section — the store includes them when they approve a return.
Understand the shipping, out-for-delivery and delivered emails
See which email a customer gets at each step of shipping, how carrier tracking sync triggers them, and how to turn them on, off or edit them.
Illustrated guide: lulu.us.com/help/understand-the-shipping-emails
Before you startShipping emails are transactional: they send regardless of marketing consent, are never sent to an erased customer, and are skipped only for a template you switched off. Automatic carrier updates need Automatic tracking (or a connected ShipStation or Shippo account).
1. Shipping confirmation
Sent when you fulfil an order and leave Send shipment details to the customer ticked. It includes the carrier and tracking link. This is the email described in fulfill-orders-tracking-and-carriers.
2. Shipping update
Sent when you change the carrier or tracking number with Edit tracking (and leave Notify customer of the change ticked), or when a connected carrier app re-sends a corrected shipment. It sends once for each distinct carrier and number. See edit-tracking-and-shipping-updates.
3. Out for delivery
Sent once when the carrier reports the parcel is out for delivery. It needs live tracking: turn on Settings > Shipping and delivery > Automatic tracking, or connect ShipStation or Shippo, which report carrier events themselves. A parcel re-shipped under a corrected number gets its own Out for delivery email.
4. Delivered
Sent when the order is marked delivered: either you select Mark as delivered on the order page, or the carrier confirms delivery and Automatically mark orders delivered is on in the Automatic tracking card.
5. Set up automatic tracking
In Settings > Shipping and delivery, in the Automatic tracking card, tick Enable automatic tracking, choose a Tracking provider (17track or AfterShip), paste its API key (the badge shows Connected) and select Save. Your store checks the carrier about every 20 minutes. The Log an Out-for-delivery event checkbox only controls the entry on the order timeline; it does not stop the Out for delivery email.
6. Follow tracking on the order
Each fulfilment card can show a status pill: Label created, Info received, In transit, Out for delivery, Delivered, Exception or Not found. Select Refresh tracking on the delivery card to check the carrier immediately; if automatic tracking is off it reminds you to turn it on in Settings > Shipping.
7. Turn each email on or off, or edit it
Go to Settings > Notifications and open Shipping updates. Open Shipping confirmation, Shipping update, Out for delivery or Delivered and edit the subject and HTML, send yourself a test, or untick Send this email. Every email in that list is now sent through its template, so your edits and the switch apply to what customers actually receive.
Completion checklist
- Automatic tracking is on (or ShipStation/Shippo is connected) if you want Out for delivery and Delivered emails from the carrier.
- You know Shipping update sends only on a real tracking change.
- You have checked each shipping template in Settings > Notifications.
Troubleshooting
The customer got no Out for delivery email.
Out for delivery needs live carrier tracking. Check Automatic tracking is enabled with a provider and a Connected API key, or that ShipStation or Shippo is connected, and that the Out for delivery template is not switched off.
The customer got a Delivered email but I never marked it delivered.
Automatically mark orders delivered is on in the Automatic tracking card, so the carrier's delivery confirmation marked it delivered. Untick it to confirm deliveries yourself.
I turned a shipping email off and it still sent.
Check you saved the template after unticking Send this email. Shipping confirmation can also be skipped per fulfilment by unticking Send shipment details to the customer.
Add payment methods: manual payments and online gateways
Turn on cash/bank payment options and connect the online payment gateways your customers can pay with, from Settings > Payments.
Illustrated guide: lulu.us.com/help/add-a-payment-method
Before you startWhile your store is in development mode, the Payments page shows a development-mode banner and every order placed at checkout is tagged "test". Configured gateways still run with whatever keys you enter, so use each provider's sandbox or test keys until you have completed Go-live (the banner links to the Go-live checklist).
1. Open Payments settings
Go to Settings > Payments in your admin.
2. Turn on manual payment methods
Under Manual payment methods, tick any of: Cash on delivery (COD), Pay at the store (pickup orders) — only selectable once a location offers Local pickup under Settings > Shipping and delivery — and Bank transfer, which reveals a Payment instructions text box (bank name, account number, reference) shown to customers on their order confirmation.
- Cash on delivery (COD)
- Pay at the store (pickup orders) — needs Local pickup turned on first
- Bank transfer — add payment instructions for customers
3. Add an online payment provider
Under Online payment providers, choose a provider from the Add a payment provider dropdown and click Add. The list is: Stripe (international cards), PayPal, PayHere, Onepay, WebXPay, PAYable and Marx IPG (card, wallet and bank gateways for Sri Lanka), plus the buy-now-pay-later options Mintpay and KOKO (3 interest-free instalments, LKR only). Each provider appears as its own card once added. At checkout, a gateway is only offered when it can accept the order's currency.
4. Enter the provider's API keys
On each provider's card, tick its enable box (Enable card payments (Stripe), Enable PayPal, or Enable {provider} for the others). PayPal and the Sri Lankan gateways also have an Environment choice: Live (real payments) or Sandbox (testing). Stripe has no Environment switch; the keys you paste decide it (test keys or live keys). Then paste the keys the provider issued you, for example Stripe's Publishable key and Secret key, or PayPal's Client ID and Secret. Once a secret is saved it only shows as a masked placeholder. Leave the field blank to keep the key that's already stored.
5. Point Stripe's webhook, if using Stripe
If you use Stripe, you can also paste its Webhook signing secret (optional) and point your Stripe webhook endpoint at /api/store/payments/webhook on your store's domain. This lets payment status updates reach your store reliably.
6. Choose how payments are captured
Under Payment capture method you can pick Automatically at checkout, Automatically when the entire order is fulfilled, or Manually. This now controls Stripe card payments: with either of the fulfilment-based options, a card is only authorized (held, not charged) at checkout, and you capture or void it from the order page — see "Capture payments later" for the full flow. PayPal and the local payment gateways (PayHere, Onepay, WebXPay, PAYable, Mintpay, KOKO, Marx) can't hold an authorization, so they always capture at checkout whatever you choose here. Pre-order deposits and gift-card-only orders also always capture at checkout. Cash on delivery, bank transfer and pay at the store are collected manually.
7. Set gift card expiration
Under Gift card expiration, choose Gift cards never expire or Gift cards expire. If they expire, enter Days after issue (a whole number from 1 to 3,650; anything else shows 'Enter a number of days between 1 and 3,650'). This applies only to new gift cards issued without an explicit expiration date. Check your local laws — some regions don't allow gift cards to expire.
8. Save
Click Save at the bottom of the Payments page. Bank installment plans (Easy payment plans) are edited on their own page and aren't affected by this Save button.
Completion checklist
- Turn on the manual methods (COD, pay at store, bank transfer) you want to offer
- Add each online gateway you have an account with from the provider dropdown
- Tick each gateway's enable box and enter its keys (sandbox or test keys while in development mode)
- Decide whether gift cards expire, and after how many days
- Complete Go-live before taking real payments
Troubleshooting
I enabled a gateway but it isn't showing at checkout.
Check that the gateway's enable box is ticked and that you clicked Save. Its required keys must be saved too, not just typed in. Also check the order's currency: some gateways only accept certain currencies (for example Mintpay and KOKO are LKR only), and a gateway that can't take the shopper's currency is hidden at checkout.
"Pay at the store" is greyed out and I can't turn it on.
This option only becomes available once a location offers Local pickup. Turn on Local pickup under Settings > Shipping and delivery first, then return to Settings > Payments.
What's the difference between Mintpay/KOKO and the Easy payment plans page?
Mintpay and KOKO are buy-now-pay-later gateways you connect here with their own merchant credentials. Easy payment plans (linked from this page) is a separate feature for listing bank card-installment schemes — each bank's tenors and handling fees — that shoppers pick from at checkout; see the bank-installments-and-bnpl article.
Can I re-enter a secret key to confirm it's correct?
No — once saved, secret keys only ever show a masked placeholder (e.g. the last 4 characters) for security. Enter a new value only if you need to replace the key; leaving the field blank keeps the existing one.
I chose "Manually" or "when fulfilled" as the capture method, but a payment was still captured straight away.
That's expected for PayPal, the Sri Lankan gateways, Marx, a pre-order deposit or a gift-card-only order — none of those can hold an authorization, so they always capture at checkout regardless of this setting. Stripe card payments do follow it: check the order's payment status shows Authorized, not Paid, right after checkout.
Capture a Stripe card payment later, instead of at checkout
Hold a customer's card at checkout and charge it only when you're ready, or when the order ships — then capture or void it from the order page.
Illustrated guide: lulu.us.com/help/capture-payments-later
Before you startThis only applies to card payments through Stripe. PayPal and the local gateways (PayHere, Onepay, WebXPay, PAYable, Mintpay, KOKO, Marx) always capture at checkout, as do pre-order deposits and gift-card-only orders.
1. Turn on delayed capture
Go to Settings > Payments and, under Payment capture method, choose Automatically when the entire order is fulfilled or Manually (instead of Automatically at checkout). Save.
2. See what happens at checkout
A customer's card is authorized — the money is held but not taken — instead of charged. The order's payment status shows Authorized, and the order page shows an Authorized badge with the amount and how long you have left. An authorization holds for 7 days; if it isn't captured by then it expires, and you'll need to ask the customer to pay again or mark the order as paid if they paid another way.
3. Capture the payment
On the order page, choose Capture payment. You can capture the full authorized amount or less — capturing less releases the rest of the hold, and the uncaptured difference is never offered to the customer as a balance due. Capturing moves the order to Paid (or Partially paid for a smaller amount). A capture that the card issuer declines fails with an error and the order stays Authorized.
4. Let fulfilment capture it instead
With "Automatically when the entire order is fulfilled" chosen, you don't need to capture by hand: the shipment that completes the whole order captures the card first, before anything is marked fulfilled. If the capture fails, that fulfilment is stopped so you're never left having shipped an order you couldn't charge — fix the card or capture a lower amount, then fulfil again.
5. Void an authorization instead of capturing it
Choose Void on the order page to release the hold on the customer's card without charging it. You can't capture it afterwards. Voiding doesn't cancel the order itself — use Cancel order separately if it won't ship.
6. Cancelling an authorized order
Cancelling an order that's still Authorized voids the card hold for you — nothing is charged. Cancelling an order that's already been captured works the normal way: it must be refunded first.
Completion checklist
- Payment capture method is set to "when fulfilled" or "Manually" (Stripe only — other gateways ignore it).
- You know an authorization expires after 7 days if nothing captures or voids it.
- Capturing less than the full amount releases the rest — it's never left as a balance due.
- Mark as paid won't work on an Authorized order — capture or void it instead.
Troubleshooting
The order's fulfilment failed and nothing shipped.
With "Automatically when the entire order is fulfilled", the shipment that completes the order tries to capture the card first. If the card can't be charged, the fulfilment is stopped so the order never ships uncharged. Capture a smaller amount or sort out the card, then fulfil again.
Can I still capture or void after the 7-day hold expires?
No — once an authorization expires, Stripe no longer holds the money. The order shows Expired; ask the customer to pay again, or use Mark as paid if they already paid you another way.
I set Payment capture method to "Manually" but a PayPal order still captured right away.
PayPal and the other local gateways can't hold an authorization, so they always capture at checkout no matter what this setting says. It only changes Stripe card payments.
Saved cards and 3D Secure for Stripe checkout
Let signed-in customers save a card for next time, and control how often Stripe asks for 3D Secure verification.
Illustrated guide: lulu.us.com/help/saved-cards-and-3d-secure
Before you startThis feature only works with Stripe, using your store's own Stripe secret key entered under Settings > Payments. It isn't available through other gateways, and it only works for signed-in customers who have confirmed their email address.
1. Open the Stripe card settings
Go to Settings > Payments. On the Stripe card, scroll to the Saved cards and 3D Secure section. Add Stripe from the Add a payment provider dropdown first if it isn't there yet.
2. Turn on saved cards
Tick Offer to save cards for future purchases. Signed-in customers with a confirmed email then see an unticked "Save this card" box at checkout — a card is only saved when the customer ticks it themselves. Saved cards live in your Stripe account (never on Lulu's servers); customers can pay with one next time or remove it from their account.
3. Set the 3D Secure threshold
In Ask 3D Secure on a customer's first N payments, enter a whole number from 0 to 10. That many of a customer's early payments will ask for 3D Secure verification, whatever their bank's own rules say. Enter 0 to let Stripe decide on every payment. After that number of payments, 3D Secure is only asked when the customer's bank requires it.
4. Save
Click Save at the bottom of the Payments page. These settings only apply to your store's Stripe gateway.
Completion checklist
- Confirm Stripe is connected with your store's own secret key
- Turn on "Offer to save cards for future purchases" if wanted
- Set how many early payments require 3D Secure (0 = let Stripe decide every time)
- Save
Troubleshooting
These controls are greyed out and show "Set by the platform".
Lulu can apply one saved-cards and 3D Secure policy to every store. While that's in place, the fields show the values being enforced and you can't change them for your store.
A customer says they can't save a card.
Saved cards only appear for signed-in customers with a confirmed email address, and only when the feature is turned on and your store is using its own Stripe secret key (not another gateway).
Why would I want 3D Secure on every early payment?
Requiring 3D Secure for a new customer's first few payments adds a verification step that can reduce fraud and chargebacks, at the cost of a slightly longer checkout. After the threshold, Lulu defers to Stripe's and the card issuer's own risk rules.
Configure the checkout page: contact, customer info, tipping and accounts
Control what customers see and enter during your single-page checkout (Contact, Delivery, Payment), including the discount code field, and set up customer accounts and Google sign-in.
Illustrated guide: lulu.us.com/help/configure-checkout-page
Before you startThese settings live at Settings > Checkout and apply to every order placed in your online store.
1. Choose the contact method
Under Customer contact method, pick Phone number or email, or Email. If you pick Phone number or email, you can also tick Require a phone number.
2. Set customer information requirements
Under Customer information, choose whether Full name needs only a last name (Only require last name) or both names (Require first and last name). Then set each of these to Don't include, Optional, or Required: Company name, Address line 2 (apartment, unit, etc.), and Shipping address phone number. The shipping address phone is separate from the contact phone.
3. Turn on marketing opt-ins
Under Marketing options, set Email marketing opt-in to Don't show, Show at checkout, or Checkout and sign-in, and SMS marketing opt-in to Don't show or Show at checkout. These add the "Email/Text me with news and offers" checkboxes.
4. Enable order notes and require policy acceptance
Under Order options, tick Let customers add an order note to show an optional note field at checkout. The note is saved on the order. Under Terms of service, tick Require customers to accept the store policies. This adds a checkbox linking to your store policies, and customers must tick it before they can place an order. Click Save in the Terms of service card to save the contact, customer information, marketing, order note and terms settings.
5. The discount code field at checkout
The order summary — in the sidebar on desktop, and in the collapsible summary on mobile — has its own discount code field; customers aren't limited to applying a code from the cart. They can apply or remove a code right there, and a code that doesn't apply shows an inline error under the field instead of failing silently. Once the customer has started paying, the field is read-only until the payment finishes or is cancelled, so the order total can't change under a payment that's already being sized.
6. Set up tipping (optional)
In the Tipping card, tick Show tipping options at checkout. Then enter the three percentages customers can choose from (Option 1, 2 and 3). Each must be a whole number from 1 to 100, and the defaults are 10, 15 and 20. The tip is worked out on the items subtotal after discounts and is added after tax, so the tip itself isn't taxed. Click Save in the Tipping card.
7. Configure customer accounts
In the Customer accounts card, tick the options you want: Show sign-in links in your online store, Require customers to sign in before checkout, Let customers request returns from their account, Let customers see and spend store credit, and Let customers sign in with Google. Google sign-in adds a "Continue with Google" button and uses the platform's shared Google sign-in by default, so there's nothing else to set up. Click Save in the Customer accounts card.
8. Optional: use your own Google sign-in client
Want Google's consent screen to show your store name instead of the platform's? Open "How to get a client ID and secret from Google" in the Your own Google sign-in client card and follow the steps to create an OAuth client in Google Cloud Console. Then paste the Client ID and Client secret and click Save. To go back to the platform sign-in, clear the Client ID and save.
Completion checklist
- Set the contact method and required customer-information fields
- Decide on email/SMS marketing opt-ins at checkout
- Turn on order notes and/or required policy acceptance
- Set up tipping presets if you want to collect tips
- Configure customer accounts (sign-in requirement, returns, store credit, Google sign-in)
- Save each card after changing it — each section saves independently
Troubleshooting
Why do Checkout, Tipping, and Customer accounts have separate Save buttons?
Each card writes its own settings. The Terms of service card's Save button saves the contact, customer information, marketing, order note and terms settings. Abandoned checkout emails, Tipping, Customer accounts and your own Google client each have their own Save button.
The "Continue with Google" button isn't showing even though I turned it on.
If the platform hasn't connected its own Google sign-in yet, the button stays hidden. It appears once the platform connects Google, or once you add your own Google client ID and secret in the Your own Google sign-in client card. Also check that Let customers sign in with Google is ticked and saved.
I set up my own Google client and now sign-in fails with redirect_uri_mismatch.
The Authorised redirect URI you added in Google Cloud Console must exactly match the URI shown in Lulu's setup steps — including after you later connect a new domain, which changes that URI and requires updating it at Google.
A customer says their discount code field at checkout showed an error and wouldn't apply.
The checkout page's discount field shows the same inline error the cart page would — an invalid, expired or inapplicable code is rejected with a message under the field, not silently ignored. If the field looks disabled instead, the customer has already started paying; it unlocks again once that payment attempt finishes or they cancel it.
Recover sales with abandoned checkout emails
Automatically email customers who start checkout but don't complete their order.
Illustrated guide: lulu.us.com/help/abandoned-checkout-emails
Before you startLulu records abandoned checkouts automatically (Orders > Abandoned checkouts). The setting below only controls whether a recovery email is sent automatically, and when. Automatic emails are off until you turn them on.
1. Open Checkout settings
Go to Settings > Checkout and find the Abandoned checkout emails card.
2. Turn on automatic emails
Tick Send abandoned checkout emails automatically.
3. Choose who receives them
Under Send to, choose Anyone who abandons checkout, or Email subscribers who abandon checkout. Email subscribers is the default, and it only emails customers who have agreed to receive marketing email.
4. Choose the delay
Under Send email, pick how long after abandonment the email goes out: 1 hour, 6 hours, 10 hours (marked Recommended, and the default) or 24 hours. Lulu checks for due emails about every 15 minutes, so an email can arrive a few minutes after the delay ends. Each abandoned checkout gets one email, and checkouts older than 7 days aren't emailed.
5. Save
Click Save under the Abandoned checkout emails card.
6. Send one recovery email manually
On Orders → Abandoned checkouts, use Send recovery email on any row to email that one checkout right away, outside the automatic schedule. Lulu refuses it for a checkout that already became an order, for an address that unsubscribed, for a non-subscriber when Send to is set to email subscribers only, or within 24 hours of the last recovery email sent to that checkout (automatic or manual) — the error names the reason. Once it sends, the row shows "Emailed {date}"; a delivery failure is reported rather than hidden, so you know to try again instead of assuming it went out.
Completion checklist
- Turn on "Send abandoned checkout emails automatically"
- Choose whether to send to everyone or only email subscribers
- Pick a delay (10 hours is the recommended default)
- Save
- Use Send recovery email on one checkout in Orders → Abandoned checkouts when you don't want to wait for the automatic schedule
Troubleshooting
A customer completed their order anyway — will they still get the email?
No, a completed checkout is no longer abandoned, so the recovery email isn't sent once an order is placed.
Should I send to everyone or only subscribers?
Sending only to Email subscribers who abandon checkout limits recovery emails to customers who already opted in to marketing email; sending to Anyone who abandons checkout reaches every incomplete checkout regardless of opt-in, which some regions restrict for non-transactional messaging — check your local marketing-email rules.
Why is 10 hours recommended?
It's marked as the recommended delay in Lulu's own settings as a balance between timeliness and giving the customer a chance to complete the order on their own.
I turned this on but no emails are going out.
If you've installed the Postbox email marketing app and turned on its abandoned checkout workflow, that workflow replaces these emails. Otherwise, check the Send to option: with Email subscribers selected, only customers who agreed to marketing email are emailed.
The Send recovery email button on Orders → Abandoned checkouts is refused.
Check the reason in the error: the checkout may have already become an order, the address may have unsubscribed, your Send to setting may be limited to subscribers and this shopper hasn't agreed to marketing email, or a recovery email (automatic or manual) already went out to that checkout in the last 24 hours.
How gift cards, store credit, and discount codes apply at checkout
Understand the order Lulu applies discounts, gift cards, and store credit in, so you can explain a customer's order total correctly.
Illustrated guide: lulu.us.com/help/gift-cards-and-store-credit-at-checkout
Before you startA customer can only redeem a gift card once it has been issued and is enabled (Products > Gift cards). Store credit can only be spent after it has been added to a customer's record, for example from a return or a manual adjustment.
1. Understand the deduction order
Lulu applies money off an order in a fixed order: discount code first, then shipping and tax are calculated on the discounted amount, then a gift card code is applied, and finally store credit covers any amount still remaining. Nothing can be spent beyond what the order actually owes.
2. Discount codes
A customer enters a discount code at checkout; it's validated and applied to eligible lines before tax and shipping are calculated. See the Create a discount article for setting up codes.
3. Gift card redemption
A customer enters a gift card code at checkout. Lulu checks that the code belongs to your store, is enabled, isn't expired, has a positive balance, and is in the same currency as the order (a gift card issued in one currency can't be spent on an order in another). Up to the full remaining balance needed is deducted and the card's balance is reduced immediately.
4. Store credit
If Let customers see and spend store credit is ticked (Settings > Checkout > Customer accounts, on by default), store credit is applied automatically to whatever is left after discounts and gift cards — but only when the customer is signed in to the account that balance belongs to. A guest who types that customer's email at checkout is not given their store credit; they see "Have store credit? Sign in to use your store credit" instead, with a link to sign in. The customer doesn't choose an amount — the full balance (up to what's owed) is applied once they're signed in. Store credit isn't applied to orders in a foreign currency, or when the order is already fully paid.
5. Gift cards as products (digital delivery)
A product marked as a gift card in your catalog is treated as digital. Nothing ships for that line, and the code is emailed once the order is paid. If the cart contains only gift-card products, cash on delivery isn't offered and local pickup (and so Pay at the store) isn't available. The customer pays online or by bank transfer, if you offer it.
Completion checklist
- Know the order money is deducted: discount, then tax/shipping on the discounted total, then gift card, then store credit
- Confirm a gift card's currency matches the order before expecting it to apply
- Remember store credit only applies for a signed-in customer, in full, not as a customer-chosen amount, and never for a guest
- Remember gift-card-only carts can't be paid with COD or Pay at the store
Troubleshooting
A customer's gift card code was rejected.
The usual reasons are: the card is disabled, has expired, has no balance left, or is in a different currency from the order (for example an LKR gift card on a USD order). Check the card under Products > Gift cards.
A customer wants to apply only part of their store credit, not all of it.
Lulu applies all available store credit automatically up to what the order owes — there's no option for the customer or merchant to choose a partial amount at checkout.
Why was a customer unable to choose cash on delivery?
If every item in the cart is a gift card (delivered by email), cash on delivery isn't offered and pickup isn't available, because there's nothing to hand over. The customer can pay online or by bank transfer, if you offer it.
A customer says they have store credit but it wasn't applied at checkout.
Store credit only applies when the customer is signed in to their own account at checkout — typing their email as a guest doesn't apply it. Ask them to sign in (the checkout page shows a "Sign in to use your store credit" link when this applies) and check the order isn't in a foreign currency, since store credit isn't spent on those.
Offer Apple Pay, Google Pay, and Link at checkout
Show one-tap wallet buttons on your product pages, cart, and checkout through Stripe's Express Checkout, on top of your regular card checkout.
Illustrated guide: lulu.us.com/help/offer-apple-pay-google-pay-and-link
Before you startExpress checkout is opt-in for each store: it stays off until you switch it on in Settings > Payments, even when Stripe is already connected. It needs card payments (Stripe) turned on first, and it uses the same prices, taxes, and shipping rates as your regular checkout.
1. Turn on Stripe first
Go to Settings > Payments and make sure Stripe is added and turned on. Express checkout settings do nothing without it; the Express checkout card shows "Turn on card payments (Stripe) above to show express checkout buttons" until it is.
2. Turn the wallets on in Stripe
In your Stripe Dashboard, open Settings > Payment methods and make sure Apple Pay, Google Pay and Link are turned on for the account (in live and in test mode).
3. Open Express checkout
Still in Settings > Payments, find the Express checkout card.
4. Turn it on
Tick Show express checkout buttons and select Save. The card shows an Off badge until you do, and nothing appears on your store until it reads On. Buttons then show only on a device that already has a wallet set up (Apple Pay on Safari/iOS, Google Pay on Chrome/Android, or Link for a returning Stripe customer), at the top of checkout, in the cart and on product pages.
5. Register your domains in Stripe
In your Stripe Dashboard, go to Settings > Payment method domains and add every domain customers check out on: your store's own domain and its www version, and any custom domain — one at a time, apex and www separately. Stripe verifies Apple Pay for you from there; Google Pay and Link use the same registered domains. Registering in live mode also registers your sandboxes.
6. Only if asked, host a domain-association file
If Stripe (or another provider) specifically asks you to host a file at /.well-known/apple-developer-merchantid-domain-association, paste its text into the Domain association file field on the Express checkout card and save — Lulu serves it on every domain of your store. Most stores never need this.
7. Check which Stripe account to use
If your store hasn't set up its own Stripe secret key, express checkout falls back to the platform's shared Stripe account — register your domains on whichever account the store actually uses.
8. Know which carts don't show wallets
Some carts use the regular checkout instead, and the shopper sees a short note where the buttons would be. When Settings > Checkout requires a company name: "Express checkout isn't available because this store needs a company name, which wallets don't share." When the store asks shoppers to accept its terms: "...because this store asks you to accept its terms at checkout." For pre-order items: "Express checkout isn't available for pre-order items — you'll confirm the pre-order terms at checkout." When nothing ships and Settings > Checkout requires address line 2, the note says the store needs an apartment, suite or unit on the billing address, which wallets rarely share. These notes show on the checkout page; the cart-specific ones also show on the cart and product page. Gift-card pages, marketplace stores, empty carts and carts with a discount code checkout would refuse also hide the buttons.
9. Required address line 2
If Settings > Checkout requires address line 2, wallets still work for shipped orders, but the address in the shopper's wallet must include it. Otherwise the shopper sees "This store needs an apartment, suite or unit (address line 2). Add it to your address (in your wallet too, if you pay with one) and try again" and nothing is charged.
Completion checklist
- Turn on Stripe before expecting express checkout buttons to appear
- Turn on Apple Pay, Google Pay and Link in your Stripe Dashboard under Settings > Payment methods
- Tick Show express checkout buttons in Settings > Payments > Express checkout and Save (it is off by default)
- Register every domain (apex and www, plus any custom domain) under Stripe's Payment method domains
- Only paste a domain-association file if Stripe specifically asks for one
- If you require address line 2, tell shoppers to add it to their wallet address
Troubleshooting
The buttons aren't showing on my test device.
Either the browser/device has no wallet set up, or the checkout needs the terms checkbox or pre-order consent accepted — express checkout always falls back to the regular checkout in those cases.
Why do I need to register my domain with Stripe at all?
Stripe verifies Apple Pay (and uses the same registration for Google Pay and Link) per domain, for security — a domain that isn't registered under Payment method domains in your Stripe account won't show the buttons.
A customer's total changed mid-payment with Apple Pay — were they charged?
No. If a discount or rate changes between opening the wallet sheet and confirming, the payment is refused before anything is charged, and the customer sees that their total changed so they can try again at the new total.
Express checkout buttons don't show on a gift-card product page.
That's expected — a gift card needs recipient details the wallet sheet doesn't collect, so express checkout is skipped there, along with marketplace stores and pre-order purchase options.
I connected Stripe but express checkout buttons never appeared.
Express checkout is opt-in per store. Open Settings > Payments > Express checkout, tick Show express checkout buttons and Save, then check the card reads On.
The buttons are hidden at checkout.
They are hidden when Settings > Checkout requires a company name, when the store requires terms to be accepted, for pre-order items, for marketplace stores, and for a cart that needs nothing paid by card. A required address line 2 hides them only on carts that ship nothing; on shipped orders the wallet address must include line 2. A required shipping phone makes the wallet sheet ask for one.
Install the Lulu POS app and choose a plan
Add the Lulu POS app to your store and pick Lite, Retail, or Pro based on how many checkout devices and cashiers you need.
Illustrated guide: lulu.us.com/help/install-pos-choose-a-plan
Before you startOnly the store owner or an administrator can add the app. Lite is free; Retail and Pro are charged in USD on top of your Lulu plan, with 0% commission on in-person sales.
1. Open Point of Sale
In the admin, click Point of Sale. If the Lulu POS app isn't added yet, you land on the Add Point of Sale page, which shows the three packages side by side.
2. Compare the plans
Lite is free and included with your Lulu plan: 1 checkout device and 2 cashier accounts, with checkout and barcode scanning, printed and email receipts, split payments and saved carts, returns at the original shop, offline cash sales, and daily sales reports with CSV export. Retail ($29/month or $290/year, 14-day free trial) gives 2 checkout devices and unlimited cashiers, and adds exchanges and store credit at the register, register hardware settings (USB or serial receipt printer and cash drawer), and per-location staff access and roles. Pro ($59/month or $590/year, 14-day free trial) gives 4 checkout devices and adds cross-branch returns and sales-by-location (branch) reports.
3. Install on Lite
Click Add for free under Lite. The app is added at no extra cost and Point of Sale opens — enough for a single till with one or two staff.
4. Upgrade to Retail or Pro
Go to Point of Sale → Settings and click Upgrade or Manage plan on the Lulu POS plan card (or open Apps → Lulu POS). On the app's plan page, choose Retail or Pro, monthly or yearly, and start the 14-day free trial.
5. Add extra checkout devices
On Retail or Pro, add Extra checkout device units ($10/month each, up to 20) on the same plan page if you need more paired devices than the plan includes. Extra devices aren't available on Lite.
6. Complete the setup checklist
Back on Point of Sale, work through the setup checklist: set a location, create a register, pair a device, set a staff PIN, and configure your receipt and tipping.
Completion checklist
- Compared Lite, Retail, and Pro against your counter's needs
- Installed the app
- Started a trial or paid for a plan if you need Retail/Pro features
Troubleshooting
Do I lose my sales history if I downgrade from Retail to Lite?
No — your orders, sessions, and reports stay. You lose the Retail-only features (exchanges and store credit at the register, register hardware settings, and per-location staff access), and any devices or cashiers over Lite's caps get a 7-day grace period before the extras are paused.
Can I try Retail or Pro without paying right away?
Yes — both have a 14-day free trial. While it runs, the plan card on Point of Sale → Settings shows the date the trial ends.
I can't see the Add for free button.
Only the store owner or an administrator can add Point of Sale. Ask one of them to add it.
Set up registers, pair checkout devices, and connect hardware
Create a register for each counter, pair the tablets or browsers that will ring up sales, and connect receipt printers, scanners, and cash drawers.
Illustrated guide: lulu.us.com/help/pos-registers-devices-hardware
Before you startLulu POS must be installed first.
1. Add a register
Go to Point of Sale → Registers → Add register. Give it a name that matches its counter, e.g. "Front counter", and choose its Location — sales on this register draw stock from that location.
2. Pair a device
Go to Point of Sale → Devices → Pair new device. Enter a device name, optionally choose the register, and click Generate code. On the tablet or computer you want to use as a till, open the /pos/pair address shown in the dialog and enter the code. The code works once and expires after 15 minutes.
3. Mind the device cap
Lite allows 1 paired device, Retail 2, and Pro 4 (plus any extra-device add-ons on Retail or Pro). Pairing beyond the cap is blocked — upgrade the plan, add an extra checkout device, or revoke an unused device first.
4. Connect hardware
On Retail and Pro, open Point of Sale → Registers, click a register, and use the Hardware section to choose the printer connection (Browser print, USB, or Serial), paper width (58 or 80 mm), copies, and auto-cut, and to turn on a cash drawer (drawer pin and when it opens). Use Test print to check it. USB and serial printers work in Chrome or Edge on a computer or Android device; iPad uses browser printing. On Lite, receipts print through the browser. A barcode scanner that types like a keyboard works without any setup.
5. Set a fallback location
On Point of Sale → Settings → Location, the Default location is used only for registers that have no location of their own. Give each register its own location where you can.
6. Test the register
On the paired device, sign in with a staff PIN, open a drawer session with your opening cash, and ring up a small cash test sale.
Troubleshooting
The pairing code says it's already used or has expired.
A pairing code works once and expires after 15 minutes. On Point of Sale → Devices, click New code (or Re-pair for a revoked device) to get a fresh one.
A device shows Paused (over plan limit).
Your plan's device count dropped (a trial ended, you downgraded, or removed extra devices) and you have more paired devices than the cap. See "What happens when you go over your POS plan's limits".
The Hardware section is locked.
Register hardware settings are available on Retail and Pro. On Lite, print receipts from the browser.
Staff PINs and POS access
Give staff a PIN so they can open a register session without sharing the owner's login, and understand who counts as a cashier under your plan.
Illustrated guide: lulu.us.com/help/pos-staff-pins-access
Before you startStaff accounts must already exist (Settings → Users). Only the store owner or an administrator can set another staff member's PIN.
1. Open Staff & PINs
Go to Point of Sale → Staff & PINs. It lists your staff with their POS access, whether a PIN is set, and their locations. If someone shows No POS access, click Give POS full access to let them use the register.
2. Set a PIN
Click Set PIN next to a staff member, enter a 4–6 digit PIN, and click Save PIN. PINs are stored hashed, never in plain text.
3. Understand cashier accounts
The first time a staff member gets a PIN or signs in to POS with a password, they become a cashier account. Lite includes 2 cashier accounts; Retail and Pro are unlimited. The store owner is never counted.
4. Change or clear a PIN
Click Change PIN to replace one, or Clear PIN to remove it — clearing a PIN frees that cashier slot and signs the staff member out of their open POS sessions.
5. Assign a location or role (Retail and Pro)
On Retail and Pro, click Edit locations next to a staff member to choose which locations they can sign in to the register at, and optionally a location role that replaces their store-wide POS permissions there.
6. Sign in at the register
On the paired device, the staff member enters their PIN (or signs in by password) to open or switch into a register session.
Troubleshooting
I can't set a PIN — it says I'm at my cashier limit.
Setting a PIN enrolls a cashier, and it is refused once you're at the plan's cap (2 on Lite). Clear an unused PIN or upgrade to Retail or Pro for unlimited cashiers.
A staff member says their POS access is paused.
If you have more cashiers than your plan allows after a downgrade, the extra accounts are paused after a 7-day grace period (the ones you choose to keep stay, then the most recently used). Upgrading or clearing another cashier's PIN brings paused cashiers back automatically. Reactivating a deactivated staff member while the cap is full keeps their admin access but pauses their POS access.
POS settings: receipts, tipping, taxes, and payment types
Configure what prints on a receipt, whether the register prompts for a tip, which payment types a cashier can take, and your offline sale limits.
Illustrated guide: lulu.us.com/help/pos-settings-receipts-tipping-payment-types
Before you startLulu POS must be added. These settings apply to every register; a register can override the tip prompt and grid mode under Registers.
1. Open POS settings
Go to Point of Sale → Settings.
2. Set the default location and receipt content
Under Location, choose a Default location — used only for registers that have no location of their own. Under Receipt, set a Header note and Footer note, and toggle Show store logo, Show tax line, Show discount line, and Show a QR code to the online store. The SMS receipts field is a note shown to staff at checkout — SMS receipts aren't sent yet.
3. Configure tipping
Under Tipping, turn on Show a tip prompt at payment, then choose whether to Allow a custom tip amount and whether to Only prompt for card tenders. Set up to 6 Suggested tip percentages (0–100%).
4. Set tax behavior
Under Taxes, list any Tax-exempt reasons a cashier can choose for a sale. The Prices include tax box is display only — it mirrors your store's tax settings; change the real setting under Settings → Taxes.
5. Choose payment types
Under Payment types, turn on the tenders your counter accepts: Cash, Card (external terminal), Gift card, Store credit, Bank transfer, and Mobile wallet. Turn on Require a reference for terminal card payments if staff must enter the terminal's approval number. Add up to 10 Custom payment types you name yourself, e.g. "Cheque". Mintpay isn't set here — it appears at the register automatically when Mintpay is switched on in Settings → Payments.
6. Require checkout information
Under Required checkout information, decide whether to require a customer email and/or phone number on every sale.
7. Set offline limits
Under Offline sales, choose whether to Allow offline card charges (cash is always allowed offline) and set a Per-transaction offline cap — the largest sale a disconnected register can queue. Leave it at 0 for no cap.
8. Set the Smart grid default
Under Smart grid, choose the Default grid mode — Smart grid or Product library — that new registers start in. Then click Save settings.
Troubleshooting
A payment type isn't showing at the register.
Turn it on under Point of Sale → Settings → Payment types. Store credit also needs a customer attached to the sale, and Mintpay needs to be switched on in Settings → Payments.
Why is there a cap on offline sales?
While a register is offline it can't check prices, stock, or payments with Lulu, so the per-transaction cap limits how large a sale can be queued until the device reconnects and the sale syncs.
Card payments go through Lulu POS?
No — card payments are taken on your own external card terminal and then recorded at the register. There is no built-in card-present terminal integration.
Sell at the register: discounts, customers, split tenders, Mintpay, and gift cards
Build a cart, attach a customer, apply a discount, split the total across payment types, take a Mintpay payment, and redeem a gift card.
Illustrated guide: lulu.us.com/help/pos-selling-mintpay-split-gift-cards
Before you startPayment types must be turned on in POS settings. Mintpay appears as a tender only when it is switched on in Settings → Payments, your store sells in LKR, and the Mintpay POS branch ID is set.
1. Build the cart
Search or scan a barcode to add products; adjust quantity and variant as needed.
2. Attach a customer
Add a customer to the sale to keep their purchase history, let them earn loyalty points if you run a loyalty program, and let them pay with their store credit.
3. Apply a discount
Tap a line and choose Apply custom discount for a percentage or amount off that item, or use Apply discount for a percentage, amount, or discount code on the whole order. A code can be typed or scanned. Custom percentage and amount discounts need the matching staff permission.
4. Start checkout
Open checkout to see the total, due amount, and any remaining balance once a split begins — the header shows "Total … · Remaining …" after the first tender.
5. Split the sale across tenders
Choose a tender (Cash, Card, Gift card, Store credit, Bank transfer, Mobile wallet, Mintpay, one of your custom types, or Custom…), enter the amount for that part, then repeat until the remaining balance reaches zero. For Card, charge the customer on your terminal first, then record it here.
6. Take a Mintpay payment
Choose Mintpay, enter the customer's Mintpay mobile number and the amount, and choose Show QR (the customer scans it in the Mintpay app) or Send SMS link. While the request is live, other tenders and Complete sale are locked until it is approved or declined. You can also print a Mintpay payment slip with the QR code for the customer to scan.
7. Know Mintpay's limits
Mintpay has no refund or cancel API from the register — removing a Mintpay leg from a split does not refund the customer; refund it from the Mintpay merchant portal instead. Mintpay is also not available on an exchange.
8. Redeem a gift card
Choose Gift card and scan or type the code. The register looks up the balance and applies the lesser of the balance and the amount due; cover any shortfall with another tender.
Troubleshooting
I removed a Mintpay tender by mistake after the customer paid.
The register warns you before removing a Mintpay leg: "The customer has already paid this with Mintpay. Removing it does not refund it." Refund it from the Mintpay merchant portal, not from the register.
Can I use Mintpay on an exchange?
No — Mintpay is disabled whenever the sale is an exchange, since exchanges are settled through the returns flow, which Mintpay doesn't support.
Offline sales and POS reports
Understand what a register can still sell when disconnected, how queued sales sync back, and where to read tender, staff, register, and hour-by-hour totals.
Illustrated guide: lulu.us.com/help/pos-offline-sales-and-reports
Before you startTurn on Allow offline card charges under Point of Sale → Settings if you want card sales recorded while disconnected.
1. Check offline readiness
The register shows a banner when it loses its connection. While offline it can still take cash, card (only if Allow offline card charges is on), and custom-payment-type sales, up to your per-transaction offline cap. Gift cards, store credit, Mintpay, bank transfer, and mobile wallet need a connection.
2. Sell while offline
Build the cart and take payment as normal; the sale is queued on the device instead of being sent to Lulu straight away.
3. Reconnect and sync
When the connection returns, queued sales sync. To check them, open the offline queue on the register (Full queue) to see each queued sale and use Retry or Retry all.
4. Resolve exceptions
If a queued sale fails to sync, check its error note and compare it with your order list and payment records before retrying. Discard removes it permanently and needs a manager PIN — only discard a sale that genuinely should not be recorded.
5. Sync queued sales promptly
The queue warns you when a sale has waited over 24 hours, and again after 72 hours. Reconnect as soon as you can. If a device or cashier was paused for going over your plan's limits, a sale queued before the pause is still accepted for up to 72 hours after the pause.
6. Open Point of Sale → Reports
Choose a date range (Today, Last 7 days, Last 30 days, Last 90 days) and optionally filter by location, register, or staff. Review the tiles: Net sales, Orders, Average sale, Tips, Refunds, Discounts, and Tax collected.
7. Break it down
Scroll to By tender, By staff, By register, By hour, Cash drawer movements, and — on Pro — By location. Sales pushed in from your own connected POS software show in a separate External POS sales block and are never counted in the register figures.
8. Export
Click Export CSV to download the report for the selected range.
Troubleshooting
A sale I took offline didn't sync.
Open the offline queue on the register and read the sale's error note, then Retry. If the device or cashier was paused for going over the plan's limits, the sale is only accepted if it was made before the pause and synced within 72 hours of it.
External POS sales aren't in my Net sales tile.
That's intentional — sales pushed in from a connected external POS system are reported separately under External POS sales, so your Lulu register figures aren't mixed with another till system's sales.
What happens when you go over your POS plan's limits
Understand the grace period, which devices and cashiers get paused first, and how to get back under your plan.
Illustrated guide: lulu.us.com/help/pos-over-cap-limits
Before you startThis applies when your Lulu POS plan allows fewer checkout devices or cashier accounts than you are using.
1. Know what triggers it
You go over the cap when your plan's allowance drops — a trial ends, you cancel or downgrade, a paid plan lapses, or you remove extra-device add-ons — while you still have more active devices or cashiers than the new plan allows.
2. The 7-day grace period
Everything keeps working for 7 days from the moment you go over cap — nothing is paused immediately.
3. What gets paused after the grace period
Once the grace period ends, only the cap's worth of devices and cashiers stay active: anything you've marked to keep is picked first, then the most recently used. The rest are paused — a device shows "Paused (over plan limit)" and keeps its pairing (no re-pairing needed later); a cashier's PIN enrollment stays, but they can't sign in.
4. Choose which to keep
On Point of Sale → Settings, the Lulu POS plan card shows a warning with Choose what to keep. Tick the devices and cashiers to keep and click Save — instead of waiting for the automatic most-recently-used pick.
5. Check what's paused
Point of Sale → Devices lists paused devices as "Paused (over plan limit)". The keep list on the plan card marks paused devices and cashiers.
6. Get back under the cap
Upgrade the plan, buy an extra-device add-on, revoke a device, or clear a cashier's PIN. Paused devices and cashiers come back automatically as soon as there's room — the ones you chose to keep first, then the most recently used.
7. Offline sales still count while paused
A sale queued offline before the pause is still accepted for up to 72 hours after the pause, so a till that was already mid-sale isn't penalized.
Troubleshooting
I upgraded — why hasn't my paused device come back?
Paused devices and cashiers are restored by an automatic check that runs within the hour (often within minutes). Saving your keep picks on the plan card runs it straight away. Then check Point of Sale → Devices.
Will I lose sales history from a paused device?
No — pausing only blocks the device or cashier from selling; it does not delete any past orders, sessions, or reports.
Generate and publish your policy pages, and set return rules
Write Refund, Privacy, Terms of service, Shipping and Contact information policies from a built-in starter template, and record your return window and fees.
Illustrated guide: lulu.us.com/help/policy-pages-and-return-rules
1. Open Policies
Go to Settings → Policies. Each of the five policies (Refund policy, Privacy policy, Terms of service, Shipping policy, Contact information) has its own card and rich text editor.
2. Start from a template
For any empty policy, click Insert template. It fills the field with a starter document that already includes your store name, store email and store address from your store details. It is only offered while the field is empty, so it can never overwrite what you have written.
3. Edit the text
Read the whole template and change the generic terms (for example the 30-day return period, refund timing and dispatch times) so they match how your store really works. Templates are drafting help, not legal advice.
4. Save
Click Save below the policy cards. A policy you clear and save is removed: its storefront page answers "not found", and it drops out of your footer, your llms.txt and the AI agent feed. Your Contact information policy is also what llms.txt and the agent feed give AI assistants as your contact details.
5. View the published policy
Click View next to a saved policy to open it on your storefront in a new tab. View is greyed out until the policy has text.
6. Record return rules
Under Return and cancellation rules, check Enable structured return rules, then set a Return window (days, 1–365, default 30) and a Restocking fee percentage (0–100; enter 0 for no fee).
7. Name final-sale collections
Optionally list Final sale collections as comma-separated collection names (for example Sale, Clearance).
8. Save return rules
Click Save in the Return and cancellation rules card. These rules are now enforced on every self-serve return request a customer makes — the window, final-sale exclusions and restocking fee shown on their order status page, and on the order's Return requested card in your admin, all come from here (or from a market's own Returns override, when one is set). They still aren't added to your refund policy PAGE automatically, so also write your return window, fees and final-sale items into the Refund policy text above if you want shoppers to read them there too.
Completion checklist
- Turned on structured return rules and set a return window and restocking fee that match how your store really works
- Listed any final-sale collections you want excluded from returns
- Know these rules are enforced on self-serve return requests but aren't auto-added to your Refund policy text
Troubleshooting
Insert template isn't showing for one of my policies.
It only appears while that policy field is empty. If there is already text, clear the field first if you really want to start over from the template.
View is greyed out next to a policy.
A policy only gets a View link once it has text. Add text and click Save first.
My return window doesn't appear on my refund policy page.
Return rules are enforced on return requests, but still aren't shown automatically on your refund policy PAGE text — add the same details to your Refund policy text and save it if you want shoppers to read them there too.
A customer says they can't request a return even though it looks like it should still be within the window.
Check whether the order belongs to a market with its own Returns override — that replaces your store-wide window, fee and final-sale list for orders placed in it. Also remember the window is counted from the delivery date, or from the last shipment if delivery was never reported, or from the order date itself for an in-store or imported order that has no shipment at all.
Customize the emails customers receive as their order moves through fulfillment
Change the subject, heading and message of order confirmation, shipping, cancellation and refund emails, and send yourself a test.
Illustrated guide: lulu.us.com/help/customize-notification-templates
Before you startSettings > Notifications has moved to a full subject + HTML editor for every email your store sends (see customize-notification-emails for the current editor). This article covers the ideas that still apply: finding a template, the Customized badge, and sending a test.
1. Open Notifications
Go to Settings → Notifications.
2. Find Customer notifications
Below Email delivery, the list shows every customer email grouped by category with its description, for example Order confirmation, Shipping confirmation, Shipping update, Out for delivery, Delivered, Order canceled, Order refund, Order edited, Return approved, Payment request and Balance received. Customer account emails such as Account invite and Customer account welcome are under Customer accounts.
3. Spot customized templates
A template you have changed shows a Customized badge next to its name.
4. Open one to edit
Click a notification to open its editor. The fields start blank when the template still uses the default text.
5. Edit the Subject and the HTML body
The editor is now Email subject plus a full Email body (HTML), not separate Heading/Body text fields — your store's logo, accent colour and footer wrap around whatever HTML you write. See customize-notification-emails for the placeholder cheat sheet and the live preview.
6. Use variables
Click a variable chip (for example {{order_name}}, {{customer_name}} or {{total}}) to copy it, then paste it into a field. Variables are replaced with the order's values when the email is sent.
7. Save
Click Save. Reset to default clears the fields; click Save afterwards to go back to the default text.
8. Send a test
Open the template again and click Send test. A copy of the saved template, filled with sample order details and with "[Test]" in front of the subject, is sent to your own staff email address.
Troubleshooting
My test email still shows the old text.
Send test email uses the saved template. Click Save first, then open the template and send the test again.
Do my edits to every email stick?
Yes. Every email in the list is sent through its template, so your edits and the Send this email switch always apply. Customer account welcome is the only one that starts switched off.
Can I change the layout or add new sections to an email?
Yes — the Email body field is now the full HTML of the email (inside your store's logo/accent/footer shell), not just text in a fixed layout. You can use table, div, p, img, a, headings, lists and inline styles; scripts, iframes, forms and event handlers aren't allowed. See customize-notification-emails.
Choose your email delivery provider and send a test email
Send customer emails through Lulu's platform sender by default, or connect your own Resend or Mailjet account to send from your own domain.
Illustrated guide: lulu.us.com/help/email-delivery-and-test-send
Before you startA Resend or Mailjet account and a verified sending domain, if you choose your own provider.
1. Open Email delivery
Go to Settings → Notifications. Email delivery is the first card.
2. Choose Send through
Keep Platform default to send through Lulu's shared sender, or choose Resend or Mailjet to send from your own domain.
3. Set your sender
If you chose your own provider, enter a Sender such as "Shop name <[email protected]>". The address must be on a domain you have verified with that provider.
4. Add your API key(s)
For Resend, paste your Resend API key. For Mailjet, paste both the Mailjet API key and the Mailjet secret key. Keys are stored encrypted and never shown again; leave a key field blank on a later save to keep the saved key.
5. Save
Click Save. You can't save Resend or Mailjet without a sender and the required key(s).
6. Send a test email
Click Send test email. A test message goes to your own staff email address through the saved settings, and the card shows either who it was sent to and how, or the reason the provider refused it.
7. Know what doesn't change
Replies to customer emails still go to your store email, whichever provider sends the message.
Troubleshooting
The test was sent through the platform provider, not my own.
The test uses your saved settings. Choose your provider, click Save, then click Send test email again.
Send test email says the provider refused it.
Check that the API key (and, for Mailjet, the secret key) is correct and that the sender's domain is verified with that provider. An unverified domain is the most common cause.
I switched back to Platform default. Do I need to delete my API keys?
No. Platform default simply stops using the saved keys. If you switch back to your own provider later, the saved keys are used again unless you enter new ones.
Staff order alerts and webhooks
Get an email when a new order or draft order comes in, and send store events to your own systems with signed webhooks.
Illustrated guide: lulu.us.com/help/staff-order-alerts-and-webhooks
1. Open Staff notifications
Go to Settings → Notifications and scroll to the Staff notifications card.
2. Choose what to be alerted on
Check New order (on by default) and/or New draft order (off by default).
3. Choose recipients
Enter up to 50 comma-separated email addresses under Additional recipients. If you enter any, alerts go to those addresses only, so include your own address if you still want them. Leave the field blank to alert the store owner only.
4. Save
Click Save in the Staff notifications card.
5. Open Webhooks
Scroll to the Webhooks card on the same page.
6. Add a webhook
Click Add webhook, enter an https:// URL on the public internet and tick at least one event (for example orders/create, orders/paid, products/update or customers/create), then click Add webhook. A store can have up to 10 webhooks.
7. Copy the signing secret
The secret is shown once, right after you add the webhook; click Copy and keep it safe. Each request carries an X-Lulu-Hmac-Sha256 header: compute the HMAC-SHA256 of the raw request body with the secret, base64-encode it and compare it to the header.
8. Test, edit, pause or remove
Use Send test to check delivery (the row shows Delivered or Failed with the HTTP status), Edit to change the URL, events or Active setting, Deactivate/Activate to pause or resume it, or Delete to remove it and free a slot.
Troubleshooting
Send test shows Failed.
Check the HTTP status shown next to Failed. A non-2xx status or "no response" means your endpoint rejected the request or could not be reached. Test the URL on its own first.
I can't save a webhook URL.
The URL must start with https:// and point to a public address; local and private network addresses are refused.
I need more than 10 webhooks.
Delete one you no longer use to free a slot. A store can have up to 10.
I added recipients and stopped getting alerts myself.
Once Additional recipients has any address, only those addresses are emailed. Add your own address to the list.
Connect WhatsApp and SMS
Send draft-order invoices to customers over WhatsApp with your own Meta Business account, and connect your own Twilio or Notify.lk account for text messages.
Illustrated guide: lulu.us.com/help/whatsapp-and-sms-notifications
Before you startA Meta Business WhatsApp Cloud API app (for WhatsApp) or a Twilio/Notify.lk account (for SMS).
1. Open Notifications
Go to Settings → Notifications and scroll to the WhatsApp Business card.
2. Create a Meta app
At developers.facebook.com, create an app, add the WhatsApp product, and find your Phone number ID under WhatsApp → API Setup.
3. Connect WhatsApp
Check Enable WhatsApp messages, paste the Phone Number ID, and paste a permanent (System User) Access token, not a temporary 24-hour one. Once a token is saved, leave the field blank to keep it.
4. Set a default country code
Optionally enter a Default country code, digits only (for example 94 for Sri Lanka), so local numbers starting with 0 are sent correctly.
5. Add an approved template (recommended)
Enter an Invoice template name for an approved WhatsApp message template with 4 body variables (name, invoice number, amount, store), and its Template language (for example en). Without one, a plain-text message is sent, which Meta only delivers within the 24-hour window after the customer last messaged you.
6. Save WhatsApp
Click Save WhatsApp. The card shows Connected once a token is saved.
7. Send an invoice over WhatsApp
When you send an invoice from a draft order whose customer has a phone number, it is sent over WhatsApp as well as by email. WhatsApp is not used for order confirmation or shipping emails.
8. Set up SMS
In the Text messages (SMS) card, choose Twilio (your account) or Notify.lk (Sri Lanka), enter the Account SID and Auth token (Twilio) or User ID and API key (Notify.lk), enter a Sender, and click Save SMS.
9. Send a test SMS
Click Send test SMS. It goes to the mobile number in your account profile. SMS is used by app features that send texts, such as auction alerts in Hammer Auctions & Offers, and only to customers who agreed to receive them.
Troubleshooting
WhatsApp messages aren't delivering outside the 24-hour window.
Without an approved message template, Meta only delivers plain-text messages within 24 hours of the customer's last message to you. Add an approved template for reliable delivery.
My access token stopped working after a day.
You probably used a temporary token. Create a permanent System User token in Meta Business Settings and save it.
Send test SMS is greyed out.
Save your SMS settings first. The test button only works once a provider is set up and there are no unsaved changes.
Cookie consent and double opt-in for email marketing
Show visitors a cookie consent banner where it's required, choose who sees it, and set your double opt-in preference for email marketing.
Illustrated guide: lulu.us.com/help/cookie-consent-and-double-optin
1. Open Customer privacy
Go to Settings → Customer privacy.
2. Choose who sees the cookie banner
Under Show the banner, pick Off, To every visitor, or In regions that require it. Off means analytics (Google Analytics) and marketing pixels (Meta, TikTok) run for every visitor unless they opted out earlier. To every visitor shows the banner to everyone and holds those pixels back until they choose. In regions that require it shows it only to visitors in the regions you list below — and to a visitor whose location can't be detected, so no one who might need it is skipped.
- Off
- To every visitor
- In regions that require it
3. Set the region list
With In regions that require it chosen, enter two-letter country codes separated by commas, or a state such as US-CA, in the Regions box. Click Use the recommended list to fill it with the EU and EEA, the UK, Switzerland, Brazil and California (California only matches when the visitor's state is known).
4. Override the banner for one market
A single market can show the banner differently from your store-wide setting: open Markets → that market → Customer privacy and choose Use store setting, To every visitor, In regions that require it, or Off for that market alone. An override can turn the banner ON for a market even where your store-wide setting is Off, but it can't turn it off for a visitor whose real location requires it under your region list.
5. Know what a visitor sees
Where the banner applies, a first-time visitor is offered Accept all, Decline, or Manage preferences (which splits Analytics and Marketing into separate switches; necessary cookies are always on). Nothing analytics- or marketing-related loads until they choose. Their choice is remembered for 180 days, and they can reopen the banner any time from the "Cookie settings" link in your store's footer.
6. What this holds back
Where the banner applies, tracking code in your theme (head snippets and custom scripts) is held back until the visitor consents, when it's recognisable as a known tracker — Google Analytics, Tag Manager and Ads, Meta, TikTok, Snap, Pinterest, Clarity and Hotjar. This check is pattern-based, so a disguised or unrecognised tag can still load before consent; load those yourself behind `window.swPixel('analytics', …)` or `'marketing'` so they wait too. Google Analytics, Meta and TikTok pixels you've connected in Analytics follow the same rule automatically.
7. Set double opt-in
Under Email marketing, turn on Require double opt-in for email marketing so new subscribers must confirm by clicking a link in an email before they're actually subscribed. Once it's on, a footer or section newsletter sign-up, the checkout marketing opt-in box, a customer's own account profile, and a marketing opt-in collected through store chat all record the shopper as PENDING and send them a confirmation email instead of subscribing them right away.
8. Know how confirmation works
The confirmation email links to a page with its own Confirm subscription button — opening the email, or a link preview or security scanner fetching it automatically, never subscribes anyone by itself. The link works for 14 days; after that, or after the shopper unsubscribes, it stops working and signing up again sends a fresh one. If someone who's already pending signs up again, Lulu won't re-send the email more than once every 10 minutes. While a subscriber is pending, they get no marketing email at all.
Completion checklist
- Chose Off, To every visitor, or In regions that require it for the cookie banner
- Set or used the recommended region list if you chose regions
- Checked any market that needs a different banner setting under Markets → that market → Customer privacy
- Linked your cookie and email practices from your Privacy policy
- Know double opt-in now sends its own confirmation email for newsletter/footer, checkout, account-profile and chat sign-ups — separately from any double opt-in setting inside the Postbox app
Troubleshooting
I set the banner to regions, but a visitor outside my list still saw it.
A visitor whose location can't be detected is shown the banner too, by design — when Lulu can't tell where someone is, it asks rather than assume they don't need it. That's different from a market-level override, which can only add the banner for a market, never remove it for a visitor whose real location requires it.
A market's Customer privacy page shows a different banner setting from my store-wide one.
That market has its own override, set under Markets → that market → Customer privacy. Choose "Use store setting" there to go back to following Settings → Customer privacy.
Will turning on double opt-in re-confirm my existing subscribers, or start sending confirmation emails?
It doesn't touch anyone already subscribed — their consent stays as it was. But from the moment you turn it on, every NEW sign-up (newsletter or footer form, checkout, account profile, chat) is recorded as pending and sent a confirmation email instead of being subscribed right away. The Postbox app has its own, separate double opt-in setting for the sign-up forms it builds.
A pixel or tracking script still runs before a visitor accepts.
Lulu can only hold back scripts it recognises as a known tracker by pattern — a disguised or unusual tag can slip through. Wrap it in `window.swPixel('analytics', function () { … })` or `'marketing'` in your theme code so it waits for consent like the rest.
Customize every notification email, with full HTML
Edit the subject and full HTML body of any email your store sends, with a placeholder cheat sheet, a live preview, and a one-click reset.
Illustrated guide: lulu.us.com/help/customize-notification-emails
Before you startGo to Settings > Notifications. Every email your store can send is listed, grouped by category: Order processing, Order exceptions, Shipping updates, Local pickup, Gift cards, Returns, Customer accounts, Email marketing, and Staff. Every email in the list is sent through its template, so your edits and the Send this email switch apply to what customers actually receive.
1. Open Notifications
Go to Settings > Notifications.
2. Spot a customized or off template
A Customized badge marks a template you have edited; Off marks one that is switched off. Most emails are on by default; Customer account welcome is the one that starts Off (see turn-on-the-customer-welcome-email).
3. Open one to edit
Click its row to open the editor.
4. Turn it on or off
Tick Send this email, only shown for emails that can be disabled; order confirmations, draft order invoices, payment requests, POS receipts, gift card emails, account invites and security emails (password reset, password changed, sign-in link) are always on. Save with the save bar.
5. Edit the subject and HTML body
Change the Email subject and the full Email body (HTML), up to 100,000 characters. Your store's logo, accent colour, and footer are added automatically around whatever you write.
6. Insert placeholders
Click a chip under Placeholders to insert it at the cursor, grouped by root — shop, customer, order, and mail-specific roots like fulfillment, refund, return, or gift_card. Loops and simple conditions are supported too, for example {% for line in order.line_items %} … {% endfor %}.
7. Watch the live preview
The Preview panel re-renders as you type, using your store's latest real order where it can. It lists errors (which stop you from saving) and warnings (for example, a placeholder that's empty on this sample order).
8. Save, send a test, or reset
Click Save. Send test emails a copy to your own staff address with "[Test]" in the subject. Reset to default clears your changes back to the built-in template — this can't be undone.
Completion checklist
- Open Settings > Notifications and find the template by category
- Edit the subject and the full HTML body, using the placeholder chips
- Fix any error shown in the preview before you can save
- Send yourself a test before relying on a change
Troubleshooting
I pasted a <script> tag and couldn't save.
Scripts, iframes, forms, and similar interactive content are never allowed in a notification email — remove it and save again.
My test email doesn't show my latest edit.
Send test uses the saved template — click Save first, then send the test again.
My earlier subject/heading/message edits disappeared.
They were moved into the new editor automatically the first time you opened this list — a one-time banner names how many. Your old wording is now the Subject and part of the HTML body.
Can I change the layout, not just the text?
Yes — the Email body (HTML) field is the whole email layout inside your store's logo/accent/footer shell, not just a text/heading pair; use table, div, p, img, a and similar tags, with inline styles.
Do all emails really use my edited template?
Yes. Every email listed in Settings > Notifications is sent through the template editor, including Shipping update, Out for delivery, Order edited, Account invite and the staff emails. A template that fails to render falls back to the built-in email rather than sending nothing.
Brand every email your store sends
Set one accent colour, logo size, and footer line that's applied automatically to every order, shipping, and account email.
Illustrated guide: lulu.us.com/help/brand-your-emails
Before you startGo to Settings > Notifications — the Email branding card is at the top of the list, above the templates themselves.
1. Open Email branding
Go to Settings > Notifications > Email branding, at the top of the list.
2. Set your accent colour
Pick it with the colour swatch or type a hex value (for example #0a5c46). It colours the top bar and the email's buttons; leave it blank to use the default.
3. Set your logo width
Enter a width in pixels, from 40 to 400. Your logo itself comes from Settings > Brand — add one there first if you haven't.
4. Add a footer line
Type a short line of text (your address, opening hours, or a note) shown at the bottom of every email.
5. Save
Click Save branding.
6. See it applied automatically
Every email your store sends through its normal senders — order, shipping, gift card, password reset, and any customized notification — picks up this branding without you editing each template individually.
7. Know what stays untouched
A store that's never saved any branding sends plain email with no accent bar, default logo handling, and no footer line — nothing changes until you save something here. Email the Lulu platform sends YOU (not your store's customers) is never branded this way.
Completion checklist
- Add a logo under Settings > Brand before setting its width here
- Pick an accent colour and a footer line, then Save branding
- Check a real store email to confirm the branding is showing
Troubleshooting
My logo isn't showing in emails.
Add a logo under Settings > Brand first — Email branding only sets its width, not the logo itself.
I set an accent colour but my emails still look plain.
Make sure you clicked Save branding (not just picked a colour), and that you're checking an email your STORE sent to a customer, not a platform email sent to you.
Can different emails have different branding?
No — one accent, logo width, and footer line apply to every store email. Edit an individual template's own HTML (see customize-notification-emails) for something email-specific.
Erase a customer's personal data
Permanently remove a customer's name, contact details, and saved cards while keeping the financial records you need to keep, for a GDPR/CCPA-style deletion request.
Illustrated guide: lulu.us.com/help/erase-a-customers-personal-data
Before you startErasing personal data helps you respond to a request — it doesn't certify your store as GDPR or CCPA compliant. You (the merchant) remain the data controller.
1. Find the request (optional)
Customers > Privacy requests lists pending erase requests, with an SLA badge (aim to act within 10 days), from customers who asked to delete their account on your storefront.
2. Open the customer and start the erase
From the request, click Review (or open the customer directly), then More actions > Erase personal data.
3. Resolve any blockers first
Lulu checks for an order that's still open (unfulfilled/partially fulfilled, or pending/authorized/partially paid), an open return, or an in-progress refund attempt. Each blocker is listed; resolve it (fulfil, cancel, or refund it) before erasing.
4. Or override as the store owner
Only the store owner can tick Erase anyway (store owner override) to erase while blockers are still open; anyone else has the button disabled until they're cleared.
5. Confirm
Tick I understand this can't be undone and click Erase personal data.
6. Know what's erased
Name, email, phone, addresses, notes, tags, and marketing consent are removed, and the customer is signed out everywhere. Their orders keep their line items, totals, taxes, dates, and refunds, with the shipping/billing address reduced to country + province. Product reviews stay but show "Anonymous". Active subscriptions are cancelled (remaining payments are never charged). Saved cards are detached from your payment provider.
7. Know what's kept
Financial records (orders, payments, refunds), gift card and store-credit balances, the audit trail, and anything already emailed or exported before the erase.
8. Installed apps are told automatically
When you erase, every installed third-party app that can see customer or order data and has a privacy contact set up receives a customer redact notice, and must delete that customer's data within 30 days. You don't have to contact them. To check, go to Customers → Privacy requests → Completed, find the request, and click Apps notified. Each app shows Scheduled, Delivered or Failed, with the number of attempts. Built-in apps and apps without a privacy contact aren't listed.
9. If a saved card couldn't be detached
The customer's data is still erased. Use Retry card detach on the customer to try again just for the card, without touching anything else.
10. Decline a request instead
From Customers > Privacy requests, click Decline on a pending request and give a reason. Nothing is erased, and the customer can ask again later.
Completion checklist
- Check Customers > Privacy requests for pending erase requests and their SLA
- Resolve any open order, return, or refund before erasing, or use the owner override
- Confirm you understand this can't be undone before erasing
- Check the customer's orders and reviews afterwards — they're kept, just anonymised
Troubleshooting
The Erase button is disabled.
You're not the store owner, and this customer has an open order, return, or refund. Resolve it, or ask the store owner to use the override.
I erased a customer but their orders are gone.
Orders are never deleted — open one and you'll see "Deleted customer" with the country and province kept for your tax records; everything else about the sale is intact.
Can I erase without being GDPR/CCPA certified?
Erasing data helps you respond to a request — Lulu doesn't certify your store as compliant. You stay the data controller and decide what obligations apply to you.
A test email to the erased customer failed to send.
That's expected — Lulu refuses to send mail to an erased customer's redacted address.
An app shows Failed under Apps notified.
Lulu retried over about 15 hours and the app's endpoint didn't accept the notice. The customer's data in Lulu is still erased. Contact the app's publisher and ask them to delete that customer's data.
Export a customer's data
Collect everything Lulu stores about a customer into a downloadable file for a data-access request, with a one-time secure link.
Illustrated guide: lulu.us.com/help/export-a-customers-data
Before you startThis is refused for a customer who's already been erased — export their data first if you might need both.
1. Open the customer
Go to Customers, open the customer, then More actions > Request customer data.
2. Request the data
The dialog lists what's collected — profile, addresses, orders and line items, consent history, reviews, gift cards (last 4 characters only), downloads, and store credit — into a JSON file and CSV spreadsheets. Click Request data.
3. Get the link
You'll see "We emailed a download link to [your address]. It works once and expires in 24 hours." The link goes to YOU, the staff member who requested it, not the customer, so you can review it first.
4. Download it
Open the email, or go to Customers > Privacy requests and use the banner for that request, then click Download export. The zip downloads once — a second click says it's already used.
5. Send it to the customer
Pass the file to the customer yourself over a secure channel — Lulu doesn't email it to them directly.
6. Installed apps are told automatically
Installed third-party apps that can see customer or order data and have a privacy contact set up receive a customer data request notice when you request the data, and must supply what they hold to you. This export contains Lulu's own data only. To check, go to Customers → Privacy requests → Completed, find the request, and click Apps notified. Built-in apps and apps without a privacy contact aren't listed.
7. Track every request
Customers > Privacy requests lists every export (and erase) request, who it came from, and when.
Completion checklist
- Request the data from the customer's More actions menu
- Open the one-time download link within 24 hours
- Pass the file to the customer yourself over a secure channel
- Check Customers > Privacy requests to see every request's history
Troubleshooting
The download link says "already used".
Each export link works exactly once — request the customer's data again if you need another copy.
The link has expired.
Export links expire 24 hours after the request — request the data again.
A very large customer's export failed.
An account with more orders, consent events, or gift cards than Lulu can safely page through in one export fails explicitly rather than silently leaving something out.
Can an erased customer's data still be exported?
No — a data request is refused once a customer has been erased.
Turn on the customer welcome email
Send a welcome email to every shopper who creates a new account on your storefront. It is off until you switch it on.
Illustrated guide: lulu.us.com/help/turn-on-the-customer-welcome-email
Before you startYou need access to Settings > Notifications. The Customer account welcome email ships switched OFF on every store, because it is sent to an address nobody has verified yet.
1. Open Notifications
Go to Settings > Notifications and scroll to the Customer accounts group.
2. Open Customer account welcome
Select the Customer account welcome row. It shows an Off badge in the list and in the editor header. The description reads "Welcome email sent when a customer creates a new account on your storefront. Off until you turn it on."
3. Tick Send this email
Tick Send this email, then save with the save bar at the top. The Off badge disappears.
4. Edit the message (optional)
Change the Email subject and Email body (HTML). Placeholders such as the shop and customer name are available; customer names are shortened to 40 characters and anything that looks like a link or contains @ is dropped from the greeting. Select Send test to email yourself a sample, or Reset to default to go back to the built-in wording.
5. Know exactly when it sends
Once on, the email is sent only when a brand-new customer registers on your storefront. It is not sent when an existing guest record is claimed, when someone signs in with Google or a sign-in link, for customers you add in the admin or at the point of sale, or for customers you import or create through the API.
6. Turn it off again
Open the same template, untick Send this email and save.
Completion checklist
- Customer account welcome shows no Off badge after saving.
- You sent yourself a test and checked the wording.
- You know it only sends for brand-new storefront registrations.
Troubleshooting
A new customer registered and got no welcome email.
The template is off by default. Turn on Send this email in Settings > Notifications > Customer accounts > Customer account welcome. Customers who registered before you turned it on are not emailed afterwards, and sign-ins with Google or a sign-in link never trigger it.
Is this the same as an account invite?
No. The welcome email goes to shoppers who register themselves. To invite a specific customer to set a password, send an account invite from their profile (send-a-customer-account-invite).
Set product pricing, compare-at price, and cost
Price a product, show a markdown with compare-at price, and track margin using cost per item.
Illustrated guide: lulu.us.com/help/set-product-pricing
Before you startDecide the selling price and, if you want to show a markdown, the original price. Have your supplier cost on hand if you want to see your margin. Note: the Pricing card described here is shown for products without variants. Once you add options such as size or colour, it is replaced by per-variant prices in the Variants table.
1. Open the Pricing section
Open Products and select a product. For a product without variants, find the Pricing card and enter the amount in the Price field — this is what the customer pays.
2. Add a compare-at price
Select the Compare-at price chip to reveal the field. Enter the original price; the storefront shows it struck through next to the price so customers see the discount.
- Leave Compare-at price empty if the product is not on sale.
- A compare-at price lower than the price isn't blocked, so check it yourself.
3. Record cost per item
Select the Cost per item chip and enter what the item costs you. Customers never see it; it is used for your profit and margin figures.
- Cost per item is also used on the Landed costs page.
- The cost is copied onto each order line when the item is sold and feeds the profit reports (see read-the-profit-reports). Changing it later does not change past orders.
4. Check the margin and profit readout
Once both Price and Cost per item are filled in, the Pricing card shows Profit (price minus cost) and Margin (profit as a percentage of price). Both update as you type.
5. Set the tax setting
Select the Charge tax chip and use the "Charge tax on this product" checkbox to control whether this product is taxed at checkout according to your tax settings.
6. Save and verify
Save the product, then open it on the storefront. Confirm the displayed price, any struck-through compare-at price, and that tax is applied as expected at checkout.
Completion checklist
- Price and (if used) compare-at price are both correct.
- Cost per item is filled in if you want to track margin.
- Charge tax reflects whether this product should be taxed.
Troubleshooting
I can't set a compare-at price, cost, or tax setting on a product with variants.
The Pricing card (with Compare-at price, Cost per item and Charge tax) is only shown for products without variants. Once a product has options, the Variants table lets you set each variant's Price, SKU, Barcode and Available quantity only. To set compare-at prices or costs per variant, use a product CSV import (Variant Compare At Price and Cost per item columns).
The margin readout shows a dash instead of a percentage.
Margin only calculates once both Price and Cost per item have a value. Fill in Cost per item to see Profit and Margin.
Can I enter a negative price?
No. Price, Compare-at price and Cost per item must be 0 or more; a negative amount is rejected on save with an error under the field.
Add and manage product images, video, and 3D models
Upload product media, choose a featured image, add alt text, and crop images.
Illustrated guide: lulu.us.com/help/manage-product-media
Before you startPrepare product photos (and, optionally, a short video or a .glb 3D model file) before you start. Each product can hold up to 250 media items.
1. Open the Media section
Open Products and select a product. The Media card shows a counter such as '3 of 250' and a grid of tiles for everything already attached.
2. Upload or link media
Select Upload (the tile in the grid, or the "Upload media" button) to choose a file from your device — images, .mp4/.webm video, or .glb 3D models — or use Add image URL, Add video URL, or Add 3D model URL to link media hosted elsewhere.
- Uploaded files are stored by Lulu; URL-added media stays hosted wherever you linked it.
3. Set the featured image
Hover a media tile and select the star icon, or open its details (pencil icon) and choose Featured image, to make it the image shown first. Only images — not video or 3D models — can be featured.
4. Add alt text
Select the pencil icon on a tile to open its details, then fill in Alt text. Alt text helps screen-reader users and feeds the product's SEO analysis.
5. Crop an image
Select the crop icon on an uploaded image tile to adjust its framing. Cropping creates a new image at the same position with the same alt text — it never destructively overwrites your original file.
- Crop is only offered for Lulu-hosted raster images, not for externally linked URLs, videos, or 3D models.
6. Remove media
Select the X icon on a tile to remove it. If you remove the featured image, the first remaining image becomes the featured one.
7. Save and check the storefront
Save the product and open it on the storefront to confirm the featured image and any video or 3D viewer display correctly. Images apply to the whole product — you can't assign an image to a specific variant.
Completion checklist
- Every image has alt text.
- The most representative image is set as Featured.
- The product preview on the storefront matches what you expect.
Troubleshooting
I can't drag images into a different order.
Drag-to-reorder isn't available for product media. Media is listed in the order it was added; remove and re-add items to change the order, and use the Featured flag to choose which image shows first.
The crop icon doesn't show on one of my images.
Crop is only available for images uploaded to Lulu's own media storage. Images added by external URL, videos, and 3D model files can't be cropped — edit the source file instead.
I'm at 250 media items and can't add more.
250 media items is the per-product limit. Remove unused images, videos or 3D files from this product to make room.
Optimize a product's search listing (SEO)
Set a product's page title, meta description, and review its search-result preview and SEO checklist.
Illustrated guide: lulu.us.com/help/optimize-product-seo
Before you startWrite the product's description first — the SEO Assistant checks it, and the search listing preview uses it when you leave the meta description blank.
1. Open the search listing preview
Open Products, select a product, and scroll to the "Search engine listing" card. It previews how the product could appear in a search result, using your store name, the product's URL, and its title and description.
2. Edit the page title and meta description
Select the pencil icon (Edit search listing) to reveal Page title (up to 70 characters) and Meta description (up to 320 characters). Leave either blank to fall back to the product's own title and description.
- The character counters update as you type.
- An error appears under a field if it fails the length check on save.
3. Check the URL handle
The URL handle field shows the product's URL slug, generated from its title when the product was created. You can edit it; when you save, Lulu offers to add a redirect from the old URL so existing links and search results keep working (see Redirect old product URLs).
4. Review the SEO Assistant
Below the search listing card, the SEO Assistant checks your focus keyphrase against the title, URL, description and image alt text, and lists an SEO checklist and a readability checklist.
- Enter a focus keyphrase — the phrase you expect customers to search for.
- Work through the flagged items; they are suggestions, not hard blockers.
5. Save and verify in search
Save the product, then check the live product page's title bar and, once Google has indexed it, the actual search snippet.
Completion checklist
- Page title is 70 characters or fewer and describes the product.
- Meta description is 320 characters or fewer and encourages a click.
- The SEO Assistant's checklist items have been reviewed.
Troubleshooting
My custom page title or meta description isn't visible on the storefront yet.
Search engines only pick up changes after they recrawl the page, which can take days. You can confirm the change is live by viewing the product page's title in your browser tab.
I changed the product's URL handle — will old links break?
Not if you keep the "Create a URL redirect" option ticked when you save: the old address then redirects permanently to the new one. You can review or remove redirects under Online Store → Preferences.
The SEO Assistant keeps flagging my image alt text.
It checks whether your focus keyphrase appears in at least one image's alt text. Add it naturally to a relevant image's Alt text field in the Media card.
Build smart collection rules and set sort order
Use condition fields, match logic, and sort order to automate which products appear in a smart collection.
Illustrated guide: lulu.us.com/help/build-smart-collection-rules
Before you startCreate the collection and choose Smart as its type — conditions only apply to smart collections, and a collection's type can't be changed after it is created. Review create-product-collections if you haven't created a collection before.
1. Choose match logic
In the Conditions card, next to "Products must match:", choose all conditions or any condition. All conditions narrows the collection; any condition widens it.
2. Pick a condition field
For each condition, choose a field: Title, Type, Vendor, Tag, or Price.
3. Choose the right relation
The relation options change by field. Title, Type and Vendor offer is equal to, is not equal to, contains, starts with, and ends with (not case-sensitive). Tag offers is equal to and is not equal to. Price offers is equal to, is not equal to, is greater than, and is less than.
- Price conditions compare against the product's lowest variant price, and the value is entered in cents — for example, enter 2500 for 25.00.
4. Add more conditions or exclude products
Select "Add another condition" to add more rules. To keep a specific product out even though it matches, use the exclude button on it in the Collection items list; excluded products are listed under "Excluded products".
5. Set the sort order
Choose a Sort order: Manually, Best selling, Product title A-Z or Z-A, Highest price, Lowest price, Newest, or Oldest. Dragging products into position is only possible in manual collections — dragging switches that collection's sort order to Manually.
6. Save and recheck membership
Save the collection. Smart collection membership is recalculated when you save the collection's conditions, and when you create or save a product, so products join or leave as they change.
Completion checklist
- Match logic (all/any) matches your intent.
- Every condition uses the right field and relation.
- Sort order is set deliberately, not left at the default.
Troubleshooting
A product I expected is missing from a smart collection.
Re-check each condition's field, relation, and value against the product's actual Title, Type, Vendor, Tag, or price. Also check whether the product is excluded, in Draft, or not visible to customers.
The sort order I picked changed to Manually.
In a manual collection, dragging a product to a new position switches the sort order to Manually. Reselect the sort order you want and avoid dragging if you want to keep it.
My price condition isn't matching what I expect.
Price conditions use the product's lowest variant price and the value is in cents — 2500 means 25.00. A value of 25 would mean 0.25. A product with one cheap variant can also match "is less than" even if most variants cost more.
Bulk-edit products from the product list
Select multiple products on the product list to change status, add tags, publish or unpublish them, delete them, or open them in the bulk editor.
Illustrated guide: lulu.us.com/help/bulk-edit-your-product-list
Before you startFilter or search the product list down to the products you intend to change before selecting them — bulk actions apply to every selected row.
1. Select products
Open Products. Use the checkbox on each row, or the header checkbox to select every row on the current page, to build your selection.
2. Edit prices, stock and more in the bulk editor
To change price, cost, SKU, stock and other fields in a spreadsheet-style grid, choose Bulk edit (up to 250 products). See use-the-bulk-editor.
3. Change status in bulk
With products selected, choose Set as active, Set as draft, Set as unlisted, or Archive from the bulk-action bar to change every selected product's status at once.
4. Add tags in bulk
Choose Add tags, enter or pick one or more tags in the dialog, then confirm. Tags are added to every selected product; tags a product already has are left alone.
5. Publish or unpublish in bulk
Choose Publish to… or Unpublish from… to add or remove every selected product from the sales channels and markets you pick.
6. Delete in bulk
Choose Delete, review the confirmation (it names how many products will be removed), and confirm. Orders that already contain those products keep their own line-item details.
- Deletion can't be undone — export the products first if you may need them again.
7. Confirm the result
After a bulk action completes, Lulu shows a toast with the result. Clear the selection and re-check the filtered list to confirm every intended product was updated.
Completion checklist
- The filtered list contains only the products you intend to change before selecting all.
- The bulk-action result toast confirms the expected count.
- Deleted products were exported first if their data might be needed later.
Troubleshooting
I need to change price or inventory for many products at once.
Select the products and choose Bulk edit to open the bulk editor grid (use-the-bulk-editor). For very large changes you can still export to CSV, edit the spreadsheet and re-import.
The bulk action button is disabled.
The buttons are disabled while a previous bulk action is still running. Wait for the message confirming it finished, then try again.
I selected products, but after changing a filter my selection disappeared.
Changing a filter re-fetches the list and clears row selection so a bulk action can never silently apply to a product you can no longer see. Reselect after filtering.
Track inventory and allow selling when out of stock
Control whether Lulu tracks a variant's stock count and whether it can still be sold once stock reaches zero.
Illustrated guide: lulu.us.com/help/set-inventory-tracking-and-policy
Before you startDecide whether you keep a real stock count for the item (a physical item) or not (a made-to-order or unlimited item). The product-level Inventory card described here is shown for products without variants.
1. Open the Inventory section of the product
Open Products and select a product without variants. Find the Inventory card, with the "Inventory tracked" switch and a stock table for your default location.
2. Turn tracking on or off
Use the Inventory tracked switch. With tracking on, the Available field is editable and stock limits what can be sold. With tracking off, the Available field is disabled and the item can always be bought regardless of count.
3. Set SKU and barcode
Open the SKU and Barcode chips to record a Stock Keeping Unit and a scannable barcode (ISBN, UPC, GTIN, etc.) for the variant.
4. Decide the out-of-stock policy
Open the Sell when out of stock chip and check Continue selling when out of stock to let customers keep ordering a tracked item after Available reaches zero — useful for backorders. Leave it unchecked to stop sales at zero.
5. Save and test
Save the product, then confirm the storefront behaves as intended: an untracked or continue-selling item stays purchasable, while a tracked item with the policy off shows as sold out at zero stock.
Completion checklist
- Track inventory quantity matches whether you keep a real stock count for this item.
- Continue selling when out of stock is set deliberately, not left at its default.
- SKU and barcode are filled in for any item you scan or reconcile against a supplier.
Troubleshooting
A customer could buy more of an item than I have in stock.
Check whether Track inventory quantity is on and Continue selling when out of stock is off for that variant. If tracking is off, Lulu never limits purchases by stock count for that item by design.
The Available field is greyed out.
Available is only editable when Track inventory quantity is on. Turn tracking on if you want to set and limit a stock count for this variant.
Where do I set stock for other locations, or for a product with variants?
The product editor shows stock for your default location only. Use the Inventory page (Products → Inventory) to view and adjust stock for each location and each variant. Note that tracking and the out-of-stock policy can only be changed in the editor for products without variants; new variants are tracked and stop selling at zero by default.
Adjust and count stock from the Inventory page
Use the dedicated Inventory page to set or adjust quantities across your catalog, record a reason, and review history.
Illustrated guide: lulu.us.com/help/adjust-and-count-stock
Before you startOpen Products → Inventory (you need the Manage inventory permission). If your store has more than one location, decide which location's stock you're updating before you start.
1. Choose a location and view
Use the location selector to pick a single location (editable), or — with more than one location — "All locations" to see the combined total. Use the view dropdown to switch between All, In stock, Low stock, Out of stock, Committed, and Not tracked. The search box matches product title, variant title and SKU.
2. Open the quantity editor
Select a variant's Available number to open its popover. Choose Adjust by to add or subtract a quantity, or Set to to enter the new total directly. Adjust by shows a live preview of the resulting new quantity.
3. Record a reason
Pick a Reason for the change: Correction (default), Count, Received, Return restock, Damaged, Theft or loss, Promotion or donation, or Other. Save to apply the change.
- Transfers and POS sales/returns write their own reasons (Transfer sent/received, POS sale/return) automatically — you don't set those by hand.
4. Review adjustment history
From the quantity popover, select View adjustment history to see every past change for that variant, including the amount, reason, and when it happened.
5. Select rows for a bulk export
Select rows (or the header checkbox) and choose "Export selected", or use the Export button at the top to export the current page, all variants, the selected rows, or everything matching your search — as a CSV for spreadsheet programs or a plain CSV. Exports follow the selected location.
6. Import quantities from CSV
Choose Import, upload a CSV exported from this page, and review the Matched/Unmatched/Will change preview before applying. Rows are matched on SKU first, then on Handle plus option values; only rows with an 'On hand (new)' value are applied, and they apply to the location you had selected.
Completion checklist
- The correct location is selected before adjusting or importing.
- Each adjustment has an accurate reason.
- A recent physical count has been reconciled using Set to or the Count reason.
Troubleshooting
I can't type a quantity in the "All locations" view.
All locations shows a combined total, which has no single place to write to. Clicking a quantity there switches to your default location and opens the editor; pick another location from the selector to edit its stock instead.
My CSV import says rows are unmatched.
Rows are matched on SKU first, then on Handle plus the variant's option values. Check that the CSV's SKU or Handle/option columns exactly match what's in the product, and that you're importing into the location you intended.
I imported a file but nothing changed.
Only rows with a value in the 'On hand (new)' column are applied. Check the Matched / Unmatched / Will change preview counts before confirming the import.
Find low-stock products before you run out
Use the Inventory page's Low stock view and threshold to spot items that need reordering.
Illustrated guide: lulu.us.com/help/monitor-low-stock-levels
Before you startDecide a stock level that counts as 'low' for your store — Lulu lets you set this threshold yourself rather than inferring it per product.
1. Open the Inventory page
Open Products → Inventory.
2. Switch to the Low stock view
Use the view dropdown and choose Low stock. An 'At or below' threshold field appears.
3. Set your threshold
Enter the quantity you consider low (it defaults to 5). The list narrows to tracked variants that are still in stock but at or below that number. Items at zero appear in the Out of stock view instead.
4. Act on the results
From this filtered list, adjust stock directly, export the list to share with a supplier, or create a purchase order for the items that need restocking.
5. Check back regularly
The Low stock view is a filter, not a standing alert — open it on a schedule (for example, before placing supplier orders) rather than expecting Lulu to notify you automatically.
Completion checklist
- The Low stock threshold matches a quantity that actually warrants reordering for this product mix.
- The correct location is selected before reading the Low stock list.
- Low-stock items have a purchase order placed or stock adjusted.
Troubleshooting
Does Lulu email or notify me when stock gets low?
No — the Low stock view is a manual filter on the Inventory page with a threshold you set. Lulu does not send an automatic notification when a variant crosses that threshold.
A variant I expect to see isn't in the Low stock list.
Check the location selector — Low stock compares the selected location's quantity (or the combined total in All locations). Untracked variants and variants already at zero aren't listed; find zero-stock items in the Out of stock view.
Sell gift cards as a product
Flag a product as a gift card so customers can buy a fixed-value voucher through your storefront.
Illustrated guide: lulu.us.com/help/sell-gift-cards-as-products
Before you startDecide the fixed denominations you want to sell (for example $25, $50, $100) — Lulu sells gift cards as regular variants, not as a customer-entered amount.
1. Create or open a product
Open Products and create a new product (or open an existing one) that will represent your gift card.
2. Turn on This product is a gift card
Find the Gift card card in the product editor and switch on "This product is a gift card". The card explains that a paid order for this product emails the buyer a voucher code instead of shipping anything.
3. Set denominations as variants
Add an option (for example 'Amount') with a value for each denomination you sell, such as $25, $50, and $100. Each resulting variant's Price is the value of that gift card.
- There is no customer-entered custom amount — every denomination is a fixed variant you define.
4. Review shipping and pricing
A gift card is delivered by email, so nothing ships. If a cart contains only gift cards, checkout skips the shipping address and shipping rates (and cash on delivery isn't offered). Review the price of each denomination in the Variants table.
5. Test a purchase
Place a test order for the gift card product and confirm the buyer receives a voucher code by email. Reconcile issued gift cards from Products → Gift cards.
Completion checklist
- Each denomination is set up as its own variant with the correct price.
- A test purchase emails a voucher code.
- A gift-card-only checkout doesn't ask for a shipping address.
Troubleshooting
Can customers type in their own gift card amount?
No — Lulu gift card products only sell the fixed denominations you create as variants. Add more variants if you want more amount choices.
Checkout is asking for a shipping address for a gift card.
Checkout only skips shipping when every item in the cart is a gift card. Confirm "This product is a gift card" was switched on and saved; if the cart also contains a regular product, shipping is still required for the order.
Where do I look up or manage a gift card after it's bought?
Open Products → Gift cards to look up issued cards, check balance and status, and see reports.
Attach pre-order and subscription purchase options to a product
Decide whether a product can be bought outright, only with a purchase option, or both, once Presale or Recur is installed.
Illustrated guide: lulu.us.com/help/attach-purchase-options-to-products
Before you startInstall Presale (for pre-orders) and/or Recur (for subscriptions) from the App Store first, and create at least one plan in that app. The Purchase options card only appears once a plan exists or one of these apps is installed.
1. Open the Purchase options card
Open Products and select a product that has an eligible purchase plan. The Purchase options card lists every selling plan currently attached — pre-order campaigns from Presale, subscriptions from Recur — with its name, type, terms, and remaining units where applicable.
2. Understand plan ownership
This list is read-only here by design — a plan is created and edited inside the app that owns it (Presale or Recur), not on the product page.
3. Choose how customers can buy
Use 'Allow customers to buy this product with or without a purchase option' to let the product sell normally and via a plan. Use 'Only display this product with these purchase options' to make the plan the only way to buy it — useful for true pre-order-only launches.
- This choice is disabled until at least one purchase option is attached, since 'only with these options' would otherwise make the product unbuyable.
4. Manage or add plans
Select 'Manage pre-orders in Presale' (or 'Install Presale from the App Store' if it isn't installed yet) to create or edit pre-order campaigns. Select 'Subscriptions' to open Recur if it's installed.
5. Save and test the buying flow
Save the product, then view it on the storefront as a customer would, confirming the purchase-option choice and checkout behavior match what you configured.
Completion checklist
- The purchase-option choice (with/without vs. only-with) matches your launch plan.
- The attached plan's terms are accurate on the product page.
- A test storefront purchase behaves as intended.
Troubleshooting
The Purchase options card isn't showing on my product.
It only appears once your store has at least one eligible plan attached, or has Presale/Recur installed. Install the relevant app, or attach a plan to this product from within that app, first.
I can't select 'Only display this product with these purchase options'.
That choice is disabled until a purchase option is actually attached to the product — otherwise nobody could buy it. Attach a plan from Presale or Recur first.
Where do I edit the pre-order plan's dates or deposit terms?
Select 'Manage pre-orders in Presale' from the Purchase options card — plan details are owned and edited inside the Presale app, not on the product page.
Sell services and non-physical products
Mark a product as non-physical, and understand what that does — and doesn't — change at checkout.
Illustrated guide: lulu.us.com/help/sell-non-physical-products
Before you startDecide whether the item actually ships. The Physical product switch only affects how the order is exported to ShipStation — it doesn't remove shipping from checkout. To deliver files automatically, attach them in the product's Digital files card (see Sell digital products).
1. Open the Shipping card
Open Products and select a product. Find the Shipping card, which has a 'Physical product' switch in its header.
2. Turn off Physical product
Switch off Physical product for a service, digital item, or anything else that doesn't need to be shipped. For a product with variants, the switch applies to the first variant only.
3. Know what changes
With Physical product off, the item is left out when the order is exported to ShipStation. Checkout still asks for a shipping address and applies your shipping rates as usual — only carts made up entirely of gift cards skip shipping. If you sell services or digital items, consider a free shipping rate (or local pickup) so customers aren't charged for delivery.
4. Decide how you deliver the item
For downloadable goods, attach the file in the product's Digital files card: paid orders then get a Download button on the order page and a downloads-ready email, with the limits you set. Gift cards automatically email a voucher code. For services, licences or anything else without a file, deliver the confirmation yourself, for example by email after the order comes in.
5. Test a purchase
Place a test order and check what the customer is asked for and charged at checkout, and that your manual delivery process is ready.
Completion checklist
- Physical product is off for every service or digital item you export to ShipStation.
- You know checkout will still ask for shipping on these items, and have a suitable rate in place.
- Digital files are attached in the Digital files card, or a manual delivery process is in place for the licence or service.
Troubleshooting
Will Lulu email my customer a download link automatically?
Yes, when the product has files attached in its Digital files card: the customer receives a downloads-ready email once the order is paid and can download from the order page. Gift cards automatically email a voucher code. For a non-physical product without files, you deliver the licence or confirmation yourself.
A cart with only non-physical items is still asking for a shipping address.
That is expected: checkout only skips the shipping step when every item in the cart is a gift card. The Physical product switch doesn't change this. Offer a free shipping rate or local pickup if you sell only non-physical items.
Does turning off Physical product affect weight or packages?
It only removes the item from ShipStation exports. Shipping rates at checkout are calculated the same way as before, and the product's Weight and Package fields stay visible — leave them empty for non-physical items.
Edit a single variant’s price, SKU, and details
Open one variant’s own page to set its price, compare-at price, cost, SKU, barcode, weight, customs information, image, and unit price.
Illustrated guide: lulu.us.com/help/edit-a-single-variant
Before you startThe product needs at least one option (such as Size or Color) so it has more than one variant. A product with no options has its price and inventory set directly on the product page instead.
1. Open the variant
Go to Products and open a product that has variants. In the Variants table, click a variant row (or its Edit link) to open that variant’s own page.
2. Review the read-only options
The Options card shows this variant’s option values (for example Size: Medium, Color: Blue) for reference. Option values themselves are edited on the product page, not here.
3. Set price, compare-at price, and cost
In the Pricing card, enter the Price customers pay, an optional Compare-at price to show a markdown, and a Cost per item to see Profit and Margin. Turn Charge tax on this variant off for a tax-exempt variant.
- A compare-at price must be left blank or be greater than the price.
4. Set SKU, barcode, and inventory
In the Inventory card, enter a SKU and Barcode, and turn Track quantity on or off. With tracking on, set the Available quantity at each location, and use Continue selling when out of stock to allow backorders.
5. Set weight and customs information
In the Shipping card (shown when Physical product is on), enter a Weight and unit, a Country/region of origin, and a Harmonized System (HS) code. Leave any of these blank to use the product’s own weight, origin, or HS code instead — the placeholder text shows what it will inherit.
6. Choose a variant image
In the Media card, select one of the product’s own images for this variant, or leave Product image selected to show the product’s featured image. Shoppers see this image once they select the matching options; add more images to the product first if the one you want isn’t listed.
7. Show a unit price
Turn on Show unit price for this variant to add a reference price such as €1.25 / 100 g. Enter the product’s total measurement (for example 750 g) and a base measure (for example per 100 g); Lulu suggests a sensible base measure for you. The Unit price preview shows exactly what shoppers will see.
8. Save
Use the save bar at the top of the page. Use the prev/next arrows next to the variant title to move to another variant without leaving the page.
Completion checklist
- Every variant that needs its own price, compare-at price, or cost has it set on its own page.
- SKU and barcode are filled in for variants you scan or track externally.
- A variant image is chosen for any variant that should show something other than the product’s featured image.
Troubleshooting
I can’t find a Pricing or Inventory card on the product page anymore.
Once a product has options, per-variant price, cost, tax, tracking, and out-of-stock policy move to each variant’s own page — open the variant from the Variants table to edit them.
The image I want isn’t in the list on the variant page.
The variant page only offers still images already uploaded to the product. Add the image in the product’s Media card first, then come back and select it.
Why does the weight field show a placeholder instead of a number?
A blank Weight on the variant means it inherits the product’s own weight — the placeholder shows that inherited value. Type a number to override it for this variant only.
Set a variant’s weight and customs information
Set a variant’s own weight, country/region of origin, and HS code for shipping labels and exports — or leave them blank to use the product’s values.
Illustrated guide: lulu.us.com/help/set-variant-shipping-and-customs
Before you startOpen the variant’s own page: Products → a product with variants → click the variant in the Variants table.
1. Open the Shipping card
On the variant page, make sure Physical product is on — it reveals the Shipping card with Weight and Customs information. A variant that isn’t a physical product (a digital item or service) hides this card, since customers won’t enter a shipping address for it.
2. Set the weight and unit
Enter a Weight and choose its unit (kg, g, lb, or oz). Leave Weight blank to use the product’s own weight — the field’s placeholder shows what will be used. A weight of 0 on the variant also falls back to the product’s weight.
3. Set the country/region of origin
Choose a Country/region of origin for customs paperwork. Leave it on “Same as product” to use the product’s own origin.
4. Set the HS code
Enter a Harmonized System (HS) code (digits and dots, up to 20 characters) used to classify the item for customs. Leave it blank to use the product’s own HS code — shown as a placeholder.
5. Save, and know what uses these values
Save the variant. Its effective weight (the variant's own weight if set, otherwise the product's) is what ShipStation exports and Shippo shipping labels use for parcel weight. Country of origin and HS code are used on the customs declaration of an international Shippo label (see add-customs-to-international-labels), where each shipped item needs an HS code and an origin. They are not yet sent on ShipStation labels or exports.
Completion checklist
- Variants that are heavier or lighter than the product’s default weight have their own weight set.
- Variants shipped from a different country, or classified differently for customs, have their own country of origin or HS code set.
- You know international Shippo labels read the HS code and country of origin from the variant (or product), and ShipStation does not use them yet.
Troubleshooting
My shipping labels show no weight, or the wrong weight.
Before this, shipping exports only read the variant’s raw weight field, which the editor never filled in — most labels carried no weight. Set a weight on the variant (or on the product, which every variant can inherit) and re-create the label.
Does the HS code or country of origin print on my shipping label's customs form?
For international labels bought through Shippo, yes: the label card builds a customs declaration from each item's HS code and country of origin (variant first, then product, then your optional Customs defaults). ShipStation labels and exports do not include them, so enter customs details in ShipStation if you use it. See add-customs-to-international-labels.
I set a weight on the product, but a specific variant still looks wrong.
Check the variant’s own Weight field — any non-zero value there overrides the product’s weight for that variant only. Clear it to go back to inheriting the product’s weight.
Assign a different image to each variant
Show shoppers the right picture for the color or style they select by assigning one of the product’s own images to a variant.
Illustrated guide: lulu.us.com/help/assign-images-to-variants
Before you startUpload the images you want to use to the product’s Media card first — the variant image picker only offers the product’s own still images, not video or 3D models, and not a new upload.
1. Open the variant
Go to Products, open a product with variants, and click a variant in the Variants table to open its own page.
2. Open the Media card
On the variant page, the Media card shows a grid: Product image (the default) plus every still image already on the product.
3. Choose the image for this variant
Select the image that matches this variant, for example the blue version of a T-shirt. Leave Product image selected to keep showing the product’s featured image for this variant.
4. Save and check the Variants table
Save the variant. The product’s Variants table shows a thumbnail of the chosen image in its Image column, and the storefront swaps to that image as soon as a shopper selects the matching options.
5. Repeat for each variant
Use the prev/next arrows on the variant page, or go back to the product and open the next variant, to assign an image to each remaining variant.
Completion checklist
- Every color or style variant that needs its own picture has one assigned.
- The images used are already uploaded to the product’s Media card.
Troubleshooting
The image I want isn’t offered on the variant page.
Only the product’s own still images (not video or 3D models) can be assigned to a variant. Upload or link the image on the product’s Media card, save the product, then open the variant again.
I removed an image from the product and now a variant looks wrong.
Removing an image that a variant was using clears that variant back to the product image automatically, so a save can never show a picture that’s no longer on the product.
Can I upload a new photo directly from the variant page?
No — the variant page only lets you choose among the product’s existing still images. Add new photos on the product’s Media card first.
Show a unit price (price per weight, volume, or measure)
Add a reference price such as €1.25 / 100 g so shoppers can compare value across pack sizes, as required in the EU and useful anywhere.
Illustrated guide: lulu.us.com/help/show-unit-prices
Before you startDecide the total measurement of what you’re selling (for example this bottle holds 750 ml) and open the variant you want to show it on — unit price is set per variant, on the variant’s own page.
1. Open the variant’s Pricing card
Go to Products, open a product, click the variant in the Variants table, and find Unit price inside the Pricing card.
2. Turn on Show unit price for this variant
A product with no options sets this on its single, implicit variant the same way.
3. Enter the total product measurement
Enter the quantity and unit the item actually contains or measures — for example 750 and ml, or 250 and g. Supported families are volume (ml, cl, l, m³), weight (mg, g, kg), length (mm, cm, m), area (m²), and item counts.
4. Choose the base measure
Pick the reference value (1, 10, 100, or 1,000) and unit to show the price per — for example per 100 g or per 1 l. Lulu suggests a sensible default (per 100 g under 250 g, otherwise per 1 kg; per 100 ml under 250 ml, otherwise per 1 l; per 1 m for length; per 1 m² for area; per item for counts), which you can change.
5. Check the preview and save
The Unit price preview shows exactly what will display, such as €1.25 / 100 g (the reference value is left out when it’s 1, so a price per liter shows as €6.00 / l). Save the variant.
6. See it on the storefront
The unit price appears under the price on the product page and in the cart and cart drawer, computed from the exact price the shopper is shown — so it always matches, even after a market price list or currency conversion. It isn’t shown for a free variant or where the math would be unreasonable (for example an extreme quantity-to-reference ratio).
Completion checklist
- The total measurement entered matches what’s actually in the package.
- The base measure makes sense for the item (grams for small weights, kilograms for larger ones, and so on).
- The preview on the variant page matches what you expect shoppers to see.
Troubleshooting
The unit price isn’t showing on the storefront.
Check that Show unit price for this variant is still on and a total measurement is entered. It’s also hidden automatically for a free variant, or when the quantity and reference measure are too far apart to show a sensible number.
Can I set the quantity and reference measure in different families, like grams and milliliters?
No — the base measure’s unit is restricted to the same family as the total measurement (both weight, both volume, both length, and so on). Changing the total measurement’s unit resets the base measure to a matching one.
Will the unit price stay correct if I sell internationally or run a sale?
Yes — Lulu computes the unit price live from the exact price shown to that shopper (after market pricing, currency conversion, and any price-list adjustment), rather than storing a fixed number, so it can never go stale.
Make a product unlisted (buyable by direct link only)
Set a product’s status to Unlisted so it’s hidden from search, collections, and recommendations, but still works for anyone with its direct link.
Illustrated guide: lulu.us.com/help/make-a-product-unlisted
Before you startDecide this is really what you want: Unlisted is different from Draft (which can’t be bought at all) and Active (which is fully listed). Unlisted sits in between — fully buyable, but not browsable.
1. Open the product and change its status
Go to Products, open the product, and in the Status field choose Unlisted instead of Active, Draft, or Archived.
2. Know what stays visible
An unlisted product’s own page still works at its usual URL, can still be added to cart, bought, and checked out, and still appears in reviews, Q&A, selling plans, wishlists, and shared cart links — anything reached directly by that product.
3. Know what gets hidden
An unlisted product disappears from collections and their counts, search, suggestions and filters, the sitemap, product feeds (Google, Meta, and AI shopping agents), recommendations and related-product lists, product card grids, menus, the comparison tool, the POS catalog, and marketplace listings.
4. Check the page isn’t indexed
The unlisted product’s page renders a noindex tag, so search engines are told not to list it even if they find the link.
5. Save and share the link
Save the product, then share its direct URL wherever you want it reachable — for example an email campaign, a social post, or a private link for a specific customer.
Completion checklist
- You chose Unlisted (not Draft) because the product should still be buyable by direct link.
- The product’s link is shared wherever you want shoppers to find it, since it won’t appear anywhere else.
- Existing marketplace listings (eBay, Amazon, and similar) are ended separately — they aren’t withdrawn automatically.
Troubleshooting
A shopper says they can’t find my unlisted product, but I gave them the link.
Unlisted products are hidden from search, collections, and every listing page on purpose — confirm you shared the exact product URL, since that’s the only way to reach it.
My marketplace listing for this product is still live after I unlisted it.
Unlisting a product doesn’t end listings already published to a connected marketplace like eBay or Amazon — end those listings on the marketplace itself.
Can I sell an unlisted product through the marketplace channel?
No — the marketplace storefront and its cart only sell active, fully listed products; an unlisted product’s page there refuses the sale.
Change a product’s URL and redirect the old one automatically
Edit a product’s URL handle and let Lulu create the 301 redirect from the old address to the new one.
Illustrated guide: lulu.us.com/help/redirect-old-product-urls
Before you startOpen the product you want to rename the URL for. Changing the handle changes the product’s live web address, so make sure you want the change before saving.
1. Open the product’s search engine listing
Go to Products, open the product, and find the URL handle field in the Search engine listing card.
2. Edit the handle
Type the new handle. It’s normalized the same way every handle is, and must stay unique in your store — a value with no letters or digits, or one already used by another product, is rejected.
3. Leave Create a URL redirect on
This checkbox defaults to on. With it checked, saving adds a redirect from the old URL to the new one under Online Store → Preferences → URL redirects, and the editor confirms with a “Redirect added” message.
4. Save
Save the product. Visitors, bookmarks, and search results still using the old URL are sent straight to the new one.
5. Know Lulu avoids redirect loops automatically
Renaming back and forth never creates a dead end: a redirect pointing at your product’s new, live address is removed automatically, chains of old redirects are flattened to point straight at the current address, and a redirect that would point a URL at itself is dropped.
Completion checklist
- The new handle reads the way you want the URL to look.
- Create a URL redirect stayed checked if anything might still link to the old URL.
- The save confirmed “Redirect added” (or warned you to add it manually — see troubleshooting).
Troubleshooting
The product saved, but I got a message that the redirect couldn’t be created.
Save still succeeds even if the redirect fails to write. Go to Online Store → Preferences and add a redirect from the old path to the new one by hand.
I renamed the product back to its original handle — will visitors to the in-between URL get stuck?
No. Lulu keeps the redirect map clean on every rename: an old redirect that would now point at a dead end is re-pointed to the current live address instead, and a self-redirect is dropped automatically.
Can I change the URL handle for a page or blog post the same way?
Pages and blog posts support the same automatic redirect on the API and CSV level, but their editors don’t yet expose an editable handle field — only the product editor and Search engine listing card do today.
I have 500 redirects already — what happens if I rename another product?
The rename and the product’s new URL still save normally; a new redirect just isn’t added once you’re at the 500-redirect cap. Remove unused redirects under Online Store → Preferences to make room.
Choose which channels and markets sell a product
Use the Publishing card to show or hide a product on specific sales channels (Online Store, POS, AI agents, and more) and in specific markets.
Illustrated guide: lulu.us.com/help/publish-products-to-channels-and-markets
Before you startThe product must be Active — a draft or archived product stays hidden everywhere regardless of these settings. By default, with nothing changed here, a product is published on every channel and every market.
1. Open the Publishing card
Go to Products, open a product, and find the Publishing card. It shows a counter such as “4 of 6 channels” over the channels your store actually has.
2. Untick a channel to hide the product there
Under Sales channels and apps, untick Online Store, Point of Sale, AI shopping agents, Headless, or a connected app’s channel (Facebook & Instagram, Google & YouTube, Marketplaces) to remove this product from that channel. A channel your store hasn’t installed is still listed, tagged Not installed, and can be set in advance.
3. Untick a market to stop selling there
Under Markets, untick a market to hide this product from shoppers whose session is in that market, on the online store and headless storefront. Leave every market ticked to sell everywhere your markets reach.
4. Read the status line
Each channel shows its own status: Published, Not published, Scheduled for …, or Published until … — see schedule-product-publishing to set a future start or end time instead of switching a channel off immediately.
5. Save
The card is part of the product’s save bar — saving the product saves its publishing rows at the same time.
6. Know what “hidden” means for shoppers
Hiding a product from a channel or market removes it from that channel’s listings, search, collections, feeds, and recommendations. A cart that already holds a line for a product you’ve since hidden keeps the line, flagged “This item is no longer available — remove it to check out,” and checkout refuses to complete while it names that line.
Completion checklist
- The product is Active — otherwise no channel or market setting here takes effect.
- Channels you don’t want to sell on (for example Point of Sale for an online-only item) are unticked.
- You know an existing cart line for a hidden product isn’t removed automatically — it’s flagged, and checkout blocks it.
Troubleshooting
I unticked a channel but the product is still showing there.
Confirm the product itself is Active — a draft or archived product is already hidden everywhere, so the Publishing card’s checkboxes don’t change anything until you activate it. Otherwise, double-check you saved the product after making the change.
The channel counter reads “3 of 4 channels” even though I see 6 channel rows.
The counter only counts channels your store currently has installed or enabled — a channel tagged Not installed is shown for reference but isn’t counted.
I hid a product from a market, but a shopper there still has it in their cart.
Hiding a product from a market doesn’t remove it from carts that already hold it. The cart and checkout flag the line as unavailable in that shopper’s country or region, and they need to remove it to pay.
Does unpublishing from a marketplace also remove my existing eBay or Amazon listing?
No — for products published through Marketplace Connect-style channel listings, you still need to end the listing on that channel yourself.
Schedule when a product goes live or comes down
Set a future publish or unpublish date and time, per channel, in your store’s own time zone.
Illustrated guide: lulu.us.com/help/schedule-product-publishing
Before you startCheck your store’s time zone under Settings → General → Time zone — the schedule you enter here is in that time zone, not UTC or your browser’s.
1. Open the Publishing card and a channel’s schedule
Go to Products, open the product, and in the Publishing card select Schedule next to the channel you want to time (for example Online Store).
2. Set Publish on and/or Unpublish on
Enter a future date and time in Publish on to keep the channel off until then, Unpublish on to automatically take it down at a future time, or both for a limited-time listing. Leave either blank for no start or end.
3. Save
The card is part of the product’s save bar. A future Publish on time is stored as not yet published; one that has already passed is saved as published right away.
4. Watch the status line update
The channel’s status shows “Scheduled for …” or “Published until …” so you can confirm the schedule without waiting for it to fire. The schedule takes effect to the second — reloading the page right after the time passes already shows it live.
5. Know that unticking a channel cancels its schedule
If you untick a channel that has a schedule, the schedule is cleared along with it — an unchecked channel never auto-publishes later on its own.
Completion checklist
- Your store’s time zone (Settings → General) is actually the one you want the schedule to use.
- A product you want to go live later is still Active — Draft and Archived stay hidden regardless of a schedule.
- Unticking a channel to cancel a schedule was intentional, since it clears the dates too.
Troubleshooting
I entered a time and got a message that it doesn’t exist.
That time falls in the hour your store’s time zone skips when clocks go forward for daylight saving — for example 2:30 a.m. on a U.S. spring-forward day. Choose a time outside that skipped hour.
My scheduled publish time passed, but the product is still hidden.
Confirm the product itself is Active and the channel was still ticked when you saved — unticking a channel removes its schedule. The schedule takes effect at the exact time regardless of whether anyone has the admin open; reload the page to see the updated status.
Can I schedule a market the same way I schedule a channel?
No — scheduling (Publish on / Unpublish on) is available per sales channel. Market availability is a simple on/off checkbox with no schedule of its own.
Sell digital products with automatic file delivery
Attach a downloadable file to a product so buyers get a secure download link by email and on their order page after they pay — no manual delivery needed.
Illustrated guide: lulu.us.com/help/sell-digital-products
Before you startDecide whether the product should skip shipping entirely. Create or open the product first; the Digital files card only appears on a saved product.
1. Turn off Physical product (optional, but usual for a pure digital item)
In the product’s Shipping card, turn off Physical product so the item isn’t asked to ship. If only some variants are digital, turn it off on those variants individually on their own variant pages instead of the whole product.
2. Open Digital files and add a file
Scroll to the Digital files card and select Add file. Allowed types are PDF, ZIP, EPUB, MP3, WAV, MP4, JPG, PNG, WebP, TXT, and CSV, up to 100 MB each and up to 20 files per product.
3. Choose which variants get the file
Use Delivered with to give the file to All variants or just one specific variant — useful when only one size or edition of the product is digital.
4. Set a download limit and expiry (optional)
Download limit caps downloads per item bought — for example a limit of 3 on a quantity-2 order gives that buyer 6 downloads total. Link expires after (days) counts from the moment the order is paid. Leave either blank for unlimited downloads or a link that never expires. Changes here only apply to purchases made after you save them.
5. Know what counts as a digital sale at checkout
A cart line counts as digital when its variant isn’t a physical product and the product has a file attached for it (or it’s a gift card). A cart made up only of digital lines skips the delivery address and shipping step, collects a billing address instead, and can’t be paid by cash on delivery.
6. See what the buyer gets
Once the order is paid, the buyer’s confirmation email shows a “Your downloads” section, and their order status page (linked from their account) shows a Download button for each file while it’s available. If the order is marked paid after the fact (bank transfer, invoice, mark as paid), a separate “Your downloads are ready” email is sent instead.
7. Remove or update a file later
Remove archives the file: it stops going to new orders, but every buyer who already has it keeps their access. To update a limit or expiry for future buyers, edit the fields on the file’s row and save — existing grants keep whatever limit and expiry they already had.
8. Give an older order access to a new file
If you add a file after some orders were already placed, select Grant to past orders on that file to give it to every paid order of the last 90 days with a matching line. This doesn’t send an email — the buyer simply sees it next time they open their order page.
Completion checklist
- Physical product is off (product-wide or per variant) for anything that shouldn’t ship.
- A download limit and expiry are set if you don’t want the file available forever.
- Older paid orders got Grant to past orders if you added the file after they bought.
Troubleshooting
My upload was refused.
Files must be one of the supported types (PDF, ZIP, EPUB, MP3, WAV, MP4, JPG, PNG, WebP, TXT, CSV) and 100 MB or smaller, and a product can hold at most 20 files. The upload is refused before it finishes if the file is too large.
A refunded customer can still see their download link.
Check whether the refund was a full refund or voided authorization — those revoke access automatically. A partial refund processed directly at your payment provider doesn’t revoke access on its own; refund the order line in Lulu’s admin instead, or revoke the download manually on the order’s Digital downloads card.
My customer says their download link says it’s expired or at its limit.
That’s the Link expires after and Download limit settings working as intended. Reset the count or extend access for that one order from the Digital downloads card on the order page in the admin.
I deleted the product — do buyers lose their files?
No — deleting a product or variant keeps the underlying files so existing buyers’ download links keep working. Duplicating a product does not copy its digital files, though; add them again on the new product.
Does checkout still ask for a shipping address if one line is digital and another is physical?
Yes — only a cart made up entirely of digital (or gift card) lines skips the shipping step. Mixing a physical item into the cart brings back the delivery address and shipping rates as usual.
Add metafields to variants and customers
Define custom fields for variants and customers, fill in their values, and decide whether the storefront may read them.
Illustrated guide: lulu.us.com/help/use-metafields-on-variants-and-customers
Before you startYou need to be able to edit products (for variants) or customers. Decide first which fields you need, for example a "Material" for variants or an internal "VIP note" for customers, and whether each may ever be shown on your storefront.
1. Open the metafield definitions
Open any variant page (Products > a product > a variant) or any customer page and find the Metafields card. Select Add definition (or Manage definitions if some already exist). This opens the Metafields page, which has four tabs: Products, Collections, Variants and Customers.
2. Add a definition
On the tab for the kind of record, select Add definition and fill in the form, then select Add definition again to save.
- Name: what you see in the editor, for example Material.
- Namespace and Key: the stable address of the field, for example custom and material (shown on the card as custom.material). Choose them carefully; themes and apps may rely on them.
- Type: Single line text, Multi-line text, Rich text, Integer, Decimal, True or false, JSON, Color, URL, Date, File, Product reference or Product list.
- Description (optional), and for some types Minimum, Maximum or Maximum length.
3. Choose Storefront access
Private — admin only is the default and keeps the value inside your admin. Visible — themes and apps can read this value makes it available to the storefront; choose it only for values you are happy for anyone to see in the page source.
4. Pin a definition (optional)
Tick Pin this definition to the top of the editor to show it first. Unpinned definitions sit behind a Show all (n) toggle on the Metafields card. You can also tick Translate this field into Sinhala and Tamil to store a separate value per language.
5. Fill in a variant's values
Go to Products, open the product, and select the variant. In the Metafields card, enter a value for each field and save with the save bar at the top. Clearing a field and saving removes the value, and a value that does not fit the field's type (for example text in an Integer field) is not saved.
6. Fill in a customer's values
Open the customer, complete the Metafields card and save the customer. Customer metafields are saved together with the rest of the profile, so you need permission to edit customers.
7. Know where values show
Private fields appear only in your admin. A Visible variant field is included in that product's data for the storefront, per variant, so a theme or app can read it. A Visible customer field is only ever available to that customer when they are signed in to their own account; it is never listed publicly. Saving a value does not add anything to your theme by itself, so a theme section or app has to display it.
8. Privacy and exports
Erasing a customer's personal data clears their metafields with the rest of the profile, and a customer data export includes them. The products CSV export, import and backup carry a variant metafields column (JSON, on variant rows; leave it blank to keep existing values).
Completion checklist
- The definition exists on the right tab (Variants or Customers).
- Storefront access is Private unless you want the storefront to read it.
- You saved the variant or customer after typing values.
- A theme section or app is set up to show any Visible field.
Troubleshooting
I cannot see the Metafields card on the variant page.
The card appears on variant and customer pages even before you have any definitions; use Add definition to create the first one. If the page itself does not open, check that your role can edit products or customers.
My value disappeared after saving.
A value that does not match the definition's type (a non-whole number in an Integer field, an invalid date or URL) is dropped rather than stored. Re-enter it in the correct format.
A Visible customer field does not show on my storefront.
Customer values are only returned to the signed-in customer in their own account data, and no theme block renders them automatically.
Can I edit metafields in the bulk editor?
No. The bulk editor covers title, status, vendor, type, tags, price, cost, SKU and similar fields, but not metafields. Edit them on each variant or customer, or use the products CSV for variant metafields.
Edit many products and variants in the bulk editor
Open a spreadsheet-style grid from the product list, choose columns, edit or paste cells, and save price, cost, stock and more across hundreds of variants at once.
Illustrated guide: lulu.us.com/help/use-the-bulk-editor
Before you startGo to Products and tick the products you want to change (up to 250). You need permission to edit products; price and cost columns need the Edit price and Edit cost permissions, and SKU, barcode, tracking and quantity need inventory permission. Columns you cannot edit are greyed, and Cost per item is hidden without View cost.
1. Open the bulk editor
On the product list, tick the rows you want. In the bulk bar select Bulk edit. The Bulk editor page opens with those products. The button is disabled when more than 250 products are selected.
- The editor loads at most 250 products and 2,000 variants. If your selection is larger, a banner says only the first products that fit are shown; edit the rest in slices.
- If you open the page with nothing selected it shows "No products to edit" and a Back to products button.
2. Understand the grid
A product with one variant is one row. A product with several variants shows a product row (title, status, vendor, type, tags) followed by one row per variant; use the arrow at the start of the row to collapse or expand its variants. The header and first column stay in view as you scroll.
3. Choose the columns
Select Columns, tick the columns you want to see and select Done. Your choice is remembered in your browser.
- Title, Status, Vendor, Type, Tags
- Price, Compare-at price, Cost per item
- SKU, Barcode
- Weight, Weight unit, HS code, Country/region of origin
- Charge tax, Track quantity, Continue selling when out of stock
- Available (default location)
4. Edit cells
Click a cell to select it and double-click (or press Enter) to edit. Enter saves the cell and moves down, Tab moves right, Esc cancels, the arrow keys move and Shift with an arrow extends the selection, and Delete clears the selected cells. Status is a drop-down (Active, Draft, Archived, Unlisted), checkbox columns toggle with a click, and Continue selling is Stop selling or Continue selling.
5. Paste, fill down and undo
Copy a block from a spreadsheet and paste it onto the grid with Ctrl+V (tab-separated cells; in checkbox columns yes, TRUE and 1 mean on). Select a range and select Fill down (or Ctrl+D) to repeat the top row through the selection. Undo reverts the last change set (an edit, a paste or a fill down counts as one); it only goes back one step.
6. Fix highlighted cells
Changed cells are highlighted. A cell with a problem shows a red dot; hover it to read the message. The checks are the same as on the single product and variant pages, for example Price is required and cannot be negative, decimals use a dot ("Use a dot for decimals, like 12.50"), Compare-at price must be above Price, Country/region of origin is two letters, HS code is digits and dots, and Available is a whole number of 0 or more. While any changed cell is invalid, Save shows "Fix the highlighted cells before saving".
7. Save
Use Save in the bar that appears at the top (Discard throws away all unsaved edits). Only the cells you changed are sent. A toast then says how many products were updated, or "X of Y products saved — Z need fixes". Cells that saved turn green and become the new starting point.
8. Handle products that did not save
Each product saves on its own and all-or-nothing: if any cell on a product is refused, nothing on that product changes. The product gets a Not saved tag, the refused cell shows the reason (hover its red dot) and the product's other edited cells say "Not saved — fix the highlighted cell on this product and try again". Correct the cell and select Save again. Other products are unaffected.
9. Understand the stock conflict check
Editing Available changes stock at your default location only, and is recorded in the inventory adjustment history with the reason bulk_edit. If the stock changed after you opened the editor (a sale, another staff member), the cell is refused with "Stock changed since you loaded this page — reload". Reload the page (the browser warns you about unsaved edits), then redo that edit against the current number.
Completion checklist
- You selected 250 or fewer products and picked the columns you need.
- No red dots are left before you select Save.
- You checked the toast for products that need fixes.
- You reloaded after a "Stock changed" message before re-entering a quantity.
Troubleshooting
The Bulk edit button is disabled.
You selected more than 250 products (hover it for the message) or a bulk action is still running. Narrow the list with filters and select fewer rows.
A column is greyed out or missing.
Your role lacks the matching permission: price and compare-at need Edit price, cost needs Edit cost (and View cost to see it), and SKU, barcode, tracking and quantity need inventory permission. The page lists the locked columns under its title.
I pressed Ctrl+Z and nothing happened.
Use the Undo button instead. It reverts only the most recent change set.
Can I edit descriptions, images, options or metafields here?
No. The grid covers the columns listed under Columns. Use the product page for descriptions, images and options, and the variant or customer page for metafields.
Quantity edits only change one location.
The Available column edits the default location. Other locations are changed on the Inventory page.
Sales channels overview: how installing an app unlocks a channel
Facebook & Instagram, Google & YouTube, Marketplace Connect, ShipStation and Shippo are App Store apps made by Lulu. Installing one adds its page to your admin and turns on its actions.
Illustrated guide: lulu.us.com/help/sales-channels-overview-install-gate
Before you startYou need the store owner account or a staff account allowed to install apps.
1. Find your sales channels
In the admin's left menu, the Sales channels group always shows Online Store, Inbox, Agentic, Point of Sale and Marketplaces (its page is readable before you install Marketplace Connect). Facebook & Instagram and Google & YouTube appear there once their app is installed; ShipStation and Shippo appear under Shipping once installed.
2. Open an uninstalled channel
If you open a channel page before installing its app (for example from a bookmark or link), you see an install card instead of an error. Free apps show "Install <App> from the App Store (free)" with a one-click install button. Marketplace Connect shows a Choose a plan button that takes you to its App Store listing, and you can still look around its page before installing.
3. Install from the card or the App Store
Click the install button on the card, or open the App Store in your admin and install Facebook & Instagram, Google & YouTube, Marketplace Connect, ShipStation or Shippo from there.
4. Know what's free
Facebook & Instagram, Google & YouTube, ShipStation and Shippo are free apps; Lulu charges nothing for them. Marketplace Connect is free while your store is in development, with up to 50 synced marketplace orders a month; once your store is live it runs on its Unlimited sync plan ($99 a month, starting with a 14-day free trial), which adds unlimited synced orders, bulk listing management and cross-region selling. Separately, you pay Meta or Google only if you run ads, and ShipStation, Shippo and carriers directly for their own plans and postage.
5. Know what stays open without installing
Your public product feeds (the Meta catalog feed and the Google Merchant Center feed) answer only while their app is installed and the feed is turned on; otherwise the feed URL answers "not found". On Marketplaces, existing connections, listings, imported orders and messages stay viewable, and you can still disconnect an account.
6. Uninstall if you stop using a channel
Uninstalling a channel's app removes its menu entry and turns off its actions (such as connecting, syncing, publishing and replying), but never deletes your existing data. Reinstall to pick up where you left off.
Troubleshooting
I installed a channel but can't see it in the menu.
Reload the admin. Facebook & Instagram and Google & YouTube appear under Sales channels (Marketplaces is always there); ShipStation and Shippo appear under Shipping.
I uninstalled Marketplace Connect. Are my existing listings gone?
No. Already-imported orders and listings stay readable. Only new connections, syncs, publishing and messaging are blocked until you reinstall.
Marketplace Connect says a marketplace can't be connected yet.
Each marketplace has to be enabled on the platform before stores can connect to it. Until then its card says so; contact Lulu support if you need it.
Create a headless storefront and get a Storefront API token
Build a custom frontend against your store's products, cart, and checkout using the Storefront API instead of a theme.
Illustrated guide: lulu.us.com/help/headless-storefront-api-token
Before you startYou need the store owner account or a staff account with the "Manage and install apps" permission. Headless storefronts aren't available for marketplace stores yet.
1. Open Headless storefronts
Go to Settings → Apps and sales channels → Headless storefronts.
2. Create a storefront
Click Create storefront, enter a Storefront name such as "Mobile app", and click Create storefront. A public token is created for it automatically.
3. Create and copy a private token
For server-side code, click Create private token on the storefront's card. The token is shown once, in the "Copy your private Storefront API token now" card. Copy it into your server-side configuration and never ship it to a browser.
4. Note the endpoint
Each storefront card shows its Endpoint, the base URL your frontend calls (it ends in /api/storefront/<version>/products), with a Copy button.
5. Use the public token in browsers
If your frontend calls the API from a browser, use the card's Public token. Under Allowed origins, click Add origin and enter each https:// origin your frontend runs on (up to 20), then Save. Leave the list empty to allow any origin, which is not recommended once you go live.
6. Mind your plan's storefront limit
The chip next to the page title shows how many storefronts you've used out of your plan's allowance. When you reach it, Create storefront is disabled until you archive one or upgrade (for example, Plus allows up to 25).
7. Archive when done
Click Archive storefront to retire one you no longer need; every token for it stops working immediately. If your plan changes and you have more storefronts than it allows, the newest ones show "Paused: over plan limit" and their tokens stop working until you archive others or upgrade.
Troubleshooting
I lost the private token.
It can't be shown again. Click Create private token to issue a new one, then click Revoke on the old one in the token list.
My browser requests are being rejected.
Add your frontend's exact https:// origin to Allowed origins and save, or leave the list empty while testing (not recommended once you go live). Browsers should use the public token, not a private one.
Is the Storefront API GraphQL?
No. It is a token-authenticated JSON (REST-style) API under /api/storefront/<version>/. Use the Read the docs link on the page for the endpoints.
External POS: see pushed sales and keep inventory in sync
Once your own in-store POS software is connected, see where its sales land in your admin and how stock stays in step between it and Lulu.
Illustrated guide: lulu.us.com/help/external-pos-orders-inventory-sync
Before you startYour POS software must already be connected from Settings → Apps and sales channels → Develop apps → Connect a POS system (see guide-connect-local-pos).
1. Find pushed sales in Orders
Go to Orders and set the channel filter to External POS to see every sale your connected POS has pushed in, alongside your online and Lulu POS orders.
2. Check the app's sync list
Go to Settings → Apps and sales channels → Develop apps and, on your POS app's card, click Recent POS syncs to see the last 20 sales it pushed, with order, receipt, location, total, payment status and time.
3. Review channel analytics
Go to Analytics; in the Sales by channel card, External POS appears as its own row, separate from Online Store and Point of Sale.
4. Review POS reports
Go to Point of Sale → Reports. External POS sales show in their own External POS sales block and are never added to your Lulu register figures.
5. Understand stock sync
Your POS reads products, locations and stock levels through the Admin API. To hear about stock changes made elsewhere (online orders, stock adjustments, received purchase orders), your POS developer can subscribe to inventory-level update webhooks or poll for recent changes.
6. Change the bound location
Sales your POS sends without naming a location are recorded at, and take stock from, the location chosen on the app's card under "Sales without a location land at". Change it there if needed.
7. Troubleshoot a missing sale
If a pushed sale doesn't appear, check Recent POS syncs, and ask your POS developer to check the error the API returned. Common causes are an unknown location or product variant, or not enough stock for an item that doesn't allow selling when out of stock.
Troubleshooting
Why don't External POS sales show in my Point of Sale → Reports totals?
They're intentionally kept in a separate block so a different till system's figures don't get mixed into your Lulu register's own numbers.
Stock went negative after a POS sale.
A sale of an item set to continue selling when out of stock can take its quantity below zero. Lulu reports that negative quantity as-is, so reconcile against it rather than treating it as an error.
Set up shipping zones and rates
Charge different shipping prices by destination country, city or postal code. Or, if you don't use zones, offer simple flat rates everywhere.
Illustrated guide: lulu.us.com/help/set-up-shipping-zones-and-rates
Before you startDecide where you'll ship to before you start. Once you add your first zone, only the countries inside your zones can check out with shipping, so add a Rest of world zone if you want to ship everywhere.
1. Open Shipping and delivery
Go to Settings > Shipping and delivery. Expand the Rates and zones row inside the Shipping card.
2. Add a shipping zone
Click Add zone and enter a Zone name (for example Domestic, Europe or Rest of world). Then pick the countries it covers. A country that another country-wide zone already covers is greyed out and labelled "In another zone", so one destination can't match two country-wide zones. Tick Rest of world (catch-all for unmatched countries) on one zone to cover every country you haven't listed elsewhere.
3. Optionally narrow a zone to cities or postal codes
In Limit to cities / postal codes (optional), list city names or postal-code prefixes separated by commas, for example Colombo, Dehiwala, 80*. End a prefix with *. A zone limited like this can share a country with a country-wide zone. Customers whose City or postal code matches get this zone's rates. Everyone else in that country gets the country-wide zone (or your Rest of world zone). Leave the box blank to serve the whole country.
4. Add rates to the zone
Under Rates for this zone, click Add rate. Enter a Rate name (for example Standard or Express), a Price, and an optional Min subtotal. A rate with a minimum only appears at checkout once the order subtotal, after discounts, reaches that amount. Each zone needs at least one rate, and you can add as many as you want customers to choose from. Click Add zone (or Save zone) to close the dialog.
5. Use flat rates if you don't need zones
Below the zones, the Shipping rates card holds flat rates, each with an optional Minimum subtotal. Flat rates only apply while you have no zones at all. Once you add a zone, checkout uses zone rates only. A customer whose country isn't in any zone (and you have no Rest of world zone) won't be offered any shipping rate and can't complete a shipped order.
6. Save and test
Click Save zones to save your zones, or Save under the Shipping rates card to save flat rates. To preview what a destination would be charged, click Calculate rates at the top of the Shipping and delivery page. The preview uses the zones and rates currently on screen and the same zone matching as checkout. It doesn't save anything.
Completion checklist
- Add a zone for each region you want to price differently
- Add a Rest of world zone if you ship everywhere, because countries outside every zone get no shipping rate
- Optionally limit a zone to specific cities or postal-code prefixes
- Give each zone at least one named rate, with an optional minimum subtotal
- Use flat rates only if you have no zones
- Preview with Calculate rates before relying on it at checkout
Troubleshooting
A customer says no shipping options appear at checkout.
Once you have any zone, only countries inside a zone get shipping rates. Flat rates are no longer used. Add the customer's country to a zone, or add a Rest of world zone. Also check that the order reaches each rate's minimum subtotal.
Can two zones cover the same country?
Two country-wide zones can't. Once a country belongs to a country-wide zone, it's greyed out in the others. A zone limited to cities or postal codes can sit inside a country that another zone already covers. Its rates win for the addresses it matches.
My city/postal scoping isn't matching.
Matching uses the customer's City field (not case sensitive) or a postal-code prefix ending in * (for example, 80* matches any postal code starting with 80). An address that matches neither gets the country-wide zone or your Rest of world zone instead.
Why doesn't a rate with a minimum subtotal show up?
A rate's minimum subtotal is compared against the order subtotal after discounts. If the order doesn't reach that amount, the rate is hidden from the customer at checkout.
Set up the boxes and envelopes you ship in
Save your package sizes so shipping rates and label purchases use the right dimensions and weight.
Illustrated guide: lulu.us.com/help/manage-shipping-packages
Before you startPackage dimensions and empty weight are used when you buy a Shippo label (the package plus the items' weight) and in the Calculate rates preview. They don't change what customers pay at checkout, because zone and flat rates are fixed prices you set.
1. Open Packages
Go to Settings > Shipping and delivery, expand the Packages row, and click Manage packages (or Add package directly from the row).
2. Choose a package type
In the Add package dialog, pick a Package type tile: Box, Envelope, or Soft package.
3. Enter dimensions and weight
Fill in Length, Width and Height and pick a Unit. Then enter Weight (empty) with its own unit. This is the weight of the empty package, which is added to the weight of the items when a Shippo label is bought.
4. Name it and save
Give the package a Package name (for example "Small box"). Tick Use as default package for all products if you want, then save. The default package is pre-selected when you buy labels, and products that don't choose their own package use it.
5. Assign a package to a product (optional)
To give one product its own package, open the product and use the Package picker in its Shipping card. Pick one of your saved packages instead of the store default.
6. Edit, set default, or delete
From the packages list, use the … menu on any package to Edit it, Set as default, or Delete it. Deleting a package never changes a product — its saved dimensions stay on the product, which simply falls back to the store default package.
Completion checklist
- Add at least one package (box, envelope, or soft package) with real dimensions and weight
- Set one as the store default
- Assign a different package to a product if it doesn't fit the default
- Remember deleting a package doesn't affect products already using it
Troubleshooting
Does changing my package sizes change what customers pay for shipping?
No. Zone and flat shipping rates are fixed prices you set, whatever the package. Packages are used when you buy a Shippo label and in the Calculate rates preview, not for the rate a customer pays at checkout.
I deleted a package a product was using — is the product broken?
No. The product keeps whatever dimensions it had saved and simply falls back to using the store's default package going forward.
Offer local delivery
Let nearby customers choose local delivery instead of a shipping rate, and deliver the order yourself.
Illustrated guide: lulu.us.com/help/offer-local-delivery
Before you startLocal delivery is one store-wide delivery area — it isn't set per location, though you can record which location it's delivered from for your own reference.
1. Open Local delivery
Go to Settings > Shipping and delivery. In the Additional delivery methods card, click Local delivery.
2. Turn it on
Tick Offer local delivery at checkout. Customers inside your delivery area will see Local delivery as an option instead of a shipping rate.
3. Describe and define your delivery area
Under How you describe the area, choose By ZIP / postal code or By radius around your shop. Either way, list the ZIP or postal codes you deliver to in ZIP / postal codes you deliver to. Separate them with commas or new lines. Spaces, dashes and capital letters are ignored. End a code with * to match everything that starts with it (SW1* matches SW1A 1AA and SW1P 3PA). If you choose a radius, customers see "Within N km of our shop" (or mi), but Lulu doesn't measure distance. Only the postal codes you list decide who can choose local delivery.
4. Limit to a country (optional)
Postal codes can repeat between countries, so set Limit to country if yours might clash with another country's codes. You can also record which location the orders are Delivered from, for your own reference.
5. Set pricing
Enter a Delivery price (0.00 for free), an optional Free local delivery over subtotal, and an optional Minimum order amount below which local delivery is hidden entirely (checked after discounts).
6. Add a note and save
In Note shown at checkout, enter something like your delivery days and hours (up to 500 characters). It appears under the Local delivery option once a customer selects it. Then click Save.
Completion checklist
- Turn on "Offer local delivery at checkout"
- List the exact ZIP/postal codes you'll deliver to (not just a radius description)
- Set a delivery price, free-over threshold, and/or minimum order amount
- Add a customer-facing note
- Save
Troubleshooting
A customer just outside my stated radius was offered local delivery.
The radius wording is descriptive text only — actual eligibility comes from the ZIP/postal codes list. Check that list rather than assuming distance is calculated.
Local delivery isn't showing for a customer who should qualify.
Check: the toggle is on, their postal code (or its prefix, if you used a * pattern) is in your list, their country matches your Limit to country setting (if set), and their order subtotal after discounts meets your Minimum order amount.
Can I offer local delivery from more than one location with different areas?
No — local delivery is one store-wide area and price. The Delivered from field is for your own records only and doesn't split the delivery area by location.
Offer local pickup at your locations
Let customers collect their online order from one or more of your store locations, free of charge.
Illustrated guide: lulu.us.com/help/offer-local-pickup
Before you startA location needs a street address before you can offer pickup there — add or edit it under Settings > Locations first.
1. Open Local pickup
Go to Settings > Shipping and delivery. In the Additional delivery methods card, click Local pickup.
2. Turn on pickup for a location
For each location you want to use, tick Offer pickup at this location. The location must have a street address and be Active. An inactive location shows a note asking you to reactivate it in Locations first.
3. Set the expected pickup time
Choose an Expected pickup time from the dropdown — this is shown to customers when they choose pickup at checkout.
4. Add pickup instructions
Write Pickup instructions (for example "Bring your order number. Pick up at the front counter, 10am to 6pm."). This text is shown at checkout and included in the "Your order is ready for pickup" email sent once you mark the order ready.
5. Save
Click Save. Local pickup is always free for the customer at checkout, so there's no price field. Pickup isn't offered when the cart contains only gift cards.
Completion checklist
- Add a street address to each location you want pickup-enabled
- Turn on "Offer pickup at this location" per location
- Set an expected pickup time
- Write clear pickup instructions (hours, counter, what to bring)
- Save — remember pickup is always free
Troubleshooting
A location doesn't show the pickup toggle, or it's disabled.
Add a location with a street address under Settings > Locations, and make sure it's marked Active. The pickup checkbox stays disabled for an inactive location until you reactivate it.
Can I charge for pickup?
No. Local pickup is always free at checkout, and there's no price setting for it. If you want to take payment in person when the customer collects, turn on Pay at the store under Settings > Payments. It's a separate setting.
Where do customers see my pickup instructions?
At checkout once they select Local pickup, and again in the "Your order is ready for pickup" email that goes out when you mark their order ready.
Connect ShipStation or Shippo, and buy shipping labels
Sync orders to ShipStation, buy and print shipping labels through Shippo, and turn on automatic carrier tracking — using your own accounts with each service.
Illustrated guide: lulu.us.com/help/connect-shipping-apps-and-labels
Before you startShipStation Connect and Shippo Shipping Labels are free apps from the App Store. If one isn't installed yet, its card offers Install free app. Lulu doesn't charge for these connections, but you pay ShipStation, Shippo or your tracking provider directly, so you need an account with each service you connect.
1. Open Shipping apps and labels
Go to Settings > Shipping and delivery, expand Shipping apps and labels, and click Manage shipping apps.
2. Connect ShipStation (optional)
Click Connect (or Install free app) on the ShipStation card and choose a mode. Custom Store (Recommended) lets ShipStation pull your orders on its own schedule and post tracking numbers back. It works on every ShipStation plan, and the page shows the credentials and the Set it up in ShipStation steps. ShipStation API key mode means you paste your ShipStation API v2 key and send orders to ShipStation from your orders list, and tracking comes back automatically. This mode needs a ShipStation Standard plan or higher. Under Sync options you can choose which order statuses ShipStation can see, include point-of-sale orders, fulfil the order automatically when ShipStation ships it, and control the shipping confirmation email.
3. Connect Shippo (optional)
Click Connect (or Install free app) on the Shippo card and paste your Shippo API token (shippo_test_… or shippo_live_…). A test token puts the connection in test mode. Once connected, add Carrier accounts (the carriers Shippo buys labels through) and set Label defaults: a Default ship-from location, a Default package and a Label format. You can also tick Fulfil the order when a label is bought, Send shipment details to the customer, and Also show my orders in the Shippo dashboard.
4. Buy a label
You buy shipping labels from the order page, not from this settings screen. Open an order and use its shipping label card: choose the package and weight, click Get rates to compare live carrier rates, then Buy label. Afterwards you can Print label, or Void label if you haven't used it. These live rates are only for buying labels. Customers still pay the zone or flat rate you set at checkout. The Shipping apps and labels screen shows how many labels you bought in the last 30 days and links to the full list (View labels). For international parcels the label card also asks for a customs declaration; see add-customs-to-international-labels.
5. Turn on automatic tracking (optional)
Back in Settings > Shipping and delivery, in the Automatic tracking card, tick Enable automatic tracking, choose a Tracking provider (17track or AfterShip — both offer a free API key), paste the API key, and optionally turn on Automatically mark orders delivered and Log an Out-for-delivery event. Lulu checks the carrier roughly every 20 minutes and updates the order automatically.
Completion checklist
- Install and connect ShipStation if you fulfil through it (Custom Store or API key mode)
- Install and connect Shippo to compare carrier rates and buy labels
- Set Shippo's label defaults (location, package, format)
- Buy labels from the order page, not from Settings
- Turn on automatic tracking with a free 17track or AfterShip key
Troubleshooting
Where do I actually buy a shipping label?
From the individual order's page, using the Shippo card there — not from Settings > Shipping and delivery, which only shows connection status and a recent-activity summary.
What's the difference between ShipStation's Custom Store and API modes?
In Custom Store mode, ShipStation pulls your orders itself using the credentials shown on the ShipStation page in Lulu, and it works on every ShipStation plan. In API key mode, you paste a ShipStation API v2 key and send orders to ShipStation from your orders list, and this needs a Standard plan or higher. Both modes send tracking numbers back to Lulu automatically.
Does Lulu take a cut of label prices or carrier rates?
No — ShipStation, Shippo, and tracking providers are connected using your own accounts and billed by them directly; Lulu doesn't charge for or mark up these connections.
My tracking isn't updating automatically.
Confirm Enable automatic tracking is on, a provider (17track or AfterShip) is selected, and a valid API key is saved (the badge shows Connected once it is). Updates run on a roughly 20-minute cycle, so allow time before assuming it's broken.
Will my customers see Shippo's live carrier rates at checkout?
No. Shippo is only used to buy labels after an order is placed. At checkout, customers see the zone, flat, local delivery or pickup options you set up under Settings > Shipping and delivery.
Limit a shipping rate by weight or order value
Offer a rate only within a price band or a weight band — for example a cheap rate under 1 kg and a pricier one above it — instead of showing every rate to every order.
Illustrated guide: lulu.us.com/help/limit-shipping-rates-by-weight-or-order-value
Before you startWorks on any zone's rates, both the general profile's zones (Settings > Shipping and delivery) and a custom shipping profile's zones.
1. Open a rate to edit
Go to Settings > Shipping and delivery, open a zone, and click Add rate (or edit an existing one).
2. Choose a condition
Set Condition to None, Based on order price, or Based on item weight.
3. Set a price band
With Based on order price, enter a Minimum order price and, optionally, a Maximum order price (leave it blank for no limit). Order price is the subtotal after discounts, and both limits are included.
4. Set a weight band
With Based on item weight, enter a Minimum weight (kg) and, optionally, a Maximum weight (kg). Weight is the items in the order plus your package, and both limits are included.
5. Save
The rate now only appears at checkout when the order falls inside the band you set — a customer outside every rate's band for that zone sees no matching rate from it.
6. Test it
Use Calculate rates at the top of Shipping and delivery with a sample order value or weight to confirm which rate wins before you rely on it at checkout.
Completion checklist
- Pick None, Based on order price, or Based on item weight for each rate
- Remember both the minimum and maximum you enter are included in the band
- Add a package weight under Settings > Shipping and delivery > Packages so weight-based rates have something to measure
- Preview with Calculate rates before you rely on a new band at checkout
Troubleshooting
I typed -1 or "abc" into a limit.
That's rejected as an invalid value as soon as you try to save — enter a number of 0 or more, or leave the field blank for no limit.
A weight-based rate never shows at checkout.
Check that your products have a weight set (on the variant, or falling back to the product), and that you have a default package set under Settings > Shipping and delivery > Packages — its weight is added to the items'.
Can one rate use both a price band and a weight band?
No — a rate has one condition type at a time. Add a second rate if you need to combine both kinds of limits.
Create a custom shipping profile for some products
Give a group of products — for example oversized or fragile items — their own shipping locations, zones and rates, instead of using your store's general profile.
Illustrated guide: lulu.us.com/help/create-shipping-profiles-for-products
Before you startEvery product starts in the General profile. A custom profile only covers the products you explicitly add to it.
1. Open shipping profiles
Go to Settings > Shipping and delivery. Below the General profile, the Custom shipping rates list shows any profiles you've created. Click Add custom profile.
2. Name the profile
Enter a Profile name — customers never see this.
3. Add products
Click Add products and search for the ones that need different shipping. A product you add here leaves whichever profile it was in before (the general profile, or another custom one); removing it from this profile returns it to general.
4. Group your shipping locations
Under Shipping from, click Add location group, name the group, and tick the locations that ship these products. A location can only belong to one group of one profile at a time — it's greyed out everywhere else once it's taken.
5. Add zones and rates to a group
Click Add zone inside the group, choose the countries it covers, and add rates exactly like the general profile's — including price/weight conditions and carrier-calculated rates.
6. Save
Checkout uses the location group that contains your default location (or the first group that has zones, if none does).
7. Know what happens when a cart mixes profiles
If a cart has products from more than one profile, rates with the same name in every profile are added together and shown as one; otherwise checkout shows a single combined "Shipping" rate, with a breakdown of each profile's share underneath it.
8. Delete a profile
Click Delete profile. Its products return to the general profile — nothing is removed from the order.
Completion checklist
- Add only the products that genuinely need different shipping to a custom profile
- Give every location group at least one zone, or its products can't be shipped from that group at all
- Check what checkout shows when a cart mixes general and custom-profile products
- Remember deleting a profile returns its products to general — it doesn't touch any existing order
Troubleshooting
Checkout says it can't ship to this address.
A profile's location group with no matching zone for that destination offers no rate at all for its products. Add a zone (or a Rest of world zone) to every group that needs one.
I added a product to a profile but its shipping price didn't change.
Check the product actually shows under this profile's Products list — if it's still listed in another profile or the general one, it's using that profile's rates instead.
Can two profiles share the same location?
No — a location belongs to one group of one profile at a time. Remove it from the other group first if you need to move it.
Show live carrier rates at checkout
Quote real-time USPS, UPS, FedEx and other carrier rates from your Shippo account at checkout, with your own markup on top, instead of only your flat rates.
Illustrated guide: lulu.us.com/help/show-live-carrier-rates-at-checkout
Before you startYou need a working Shippo connection and a complete origin address before carrier rates can show at checkout.
1. Connect Shippo
Go to Settings > Shipping and delivery > Shipping apps and labels and click Connect (or Install free app) on the Shippo card, then paste your Shippo API token.
2. Give your shipping location a full address
Carrier rates need an origin — make sure the location that ships (your default location, or the first in the group) has a complete street, city, postal code and country under Settings > Locations. Without one, checkout shows your flat rates instead.
3. Check the status banner
At the top of Settings > Shipping and delivery (and inside the zone's carrier-rates box as soon as you tick it) a banner tells you whether carrier rates can work. Connect Shippo: Shippo isn't connected, use Connect Shippo. Reconnect Shippo: the connection needs attention, use Open Shippo. Add a ship-from address: there is no active location to ship from, add one in Settings > Locations. Complete your ship-from address: it lists the missing fields, use Edit locations. Carrier rates are ready: everything is in place. No banner appears while no zone has carrier rates turned on. Every warning means checkout shows the zone's flat rates meanwhile.
4. Turn on carrier rates for a zone
Open a zone (in the general profile or a custom profile) and, under Carrier-calculated rates, tick Show live carrier rates at checkout (Shippo).
5. Choose carriers and services (optional)
Tick specific carriers — USPS, UPS, FedEx, DHL Express, Canada Post, Australia Post, Royal Mail, Aramex — to limit what's offered; leave all unticked to offer every carrier on your Shippo account. You can also list specific Shippo service tokens, separated by commas, to narrow it further.
6. Add your own markup
Set Adjust by % and Adjust by amount. Customers pay the carrier's price × (1 + %) + the amount; use a negative percentage to discount the carrier's price instead.
7. Add handling time
Set Handling time (days) — it's added to the delivery estimate shown to the customer alongside the carrier's own transit time.
8. Decide whether to keep showing flat rates too
Tick Show flat rates too to list your flat rates alongside carrier rates always; leave it off and your flat rates only appear as a fallback if Shippo can't be reached.
9. Test it
Use Calculate rates, or check out to a real address, to see named carrier services with your markup and an estimated delivery window.
10. Know how quotes are calculated
The customer's full delivery address (street, line 2, state, postal code, and whether it's a company) is sent to the carrier, so residential and rural surcharges are included. If Shippo quotes in a currency other than your store's, Lulu converts the quote at current exchange rates before applying your markup. If current rates are unavailable, or the currency isn't a two-decimal one, that quote isn't offered and your flat rates show. Express wallets only know the country, state, city and postal code, so they quote on those.
Completion checklist
- Connect Shippo and give your shipping location a complete address first
- Turn on carrier rates per zone, and optionally limit which carriers or services are offered
- Set a % and/or fixed markup — customers never see your raw carrier cost without it
- Decide whether flat rates stay visible alongside carrier rates, or only appear as a fallback
- Read the status banner in Settings > Shipping and delivery — it tells you why flat rates are showing
Troubleshooting
Checkout is showing my flat rates instead of carrier rates.
That's the designed fallback — Shippo couldn't answer (a bad token, a missing or incomplete ship-from address, an incomplete destination, or a timeout). Checkout always falls back to flat rates so customers can still check out. The status banner in Settings > Shipping and delivery names the cause when it's on your side.
Rates seem slow to reflect a change I just made.
Carrier quotes are cached for up to 20 minutes to keep checkout fast. A markup or carrier-list change you save takes effect on the next quote, not instantly for a shopper already mid-checkout.
A carrier rate isn't showing even though Shippo is connected.
Check which carriers and services you've ticked, as only those are offered. Quotes in another currency are converted to your store's currency, but a quote is dropped when current exchange rates aren't available or the currency isn't a two-decimal one.
Add a customs declaration to an international shipping label
Set HS codes and countries of origin, save customs defaults, and buy cross-border Shippo labels that carry a customs declaration built from the order.
Illustrated guide: lulu.us.com/help/add-customs-to-international-labels
Before you startCustoms declarations are built for labels bought with the Shippo Shipping Labels app (see connect-shipping-apps-and-labels). Your ship-from location needs a full address with a country. Domestic labels are unchanged and show no customs section.
1. Know when customs applies
The Customs declaration section appears on the order's Shipping label card only when the destination country differs from the country of the Ship from location. Shipments between two EU member countries, and between the US and its territories (PR, VI, GU, AS, MP), are treated as domestic and skip customs.
2. Give each item an HS code and origin
Open the variant (Products > a product > a variant) and fill in HS code and Country/region of origin in its Shipping card; leave them blank to use the product's own values. The bulk editor has the same two columns for many variants at once. See set-variant-shipping-and-customs.
3. Save customs defaults (optional)
Go to Settings > Shipping and delivery and find the Customs defaults card. Fill in what you want to reuse, then select Save customs defaults ("Customs defaults updated").
- Default HS code and Default country of origin: used only for items that have none of their own, and only when you tick the box on a label.
- Contents type: Merchandise, Gift, Commercial sample, Documents, Returned goods or Other.
- If it can't be delivered: Return to sender or Abandon.
- Signer (store's legal name): certifies the declaration; if blank your store name is used.
- Duties and taxes: Recipient pays on arrival (DDU) or I pay in advance (DDP).
- Minimum item value: what is declared for free or gift items priced 0.00 (default 1.00). Enter 0 to block labels that contain such an item.
4. Open the Shipping label card on the order
Open the order. On the Shipping label card choose the Ship from location, the Package and the Total weight, and tick the items to ship. When the parcel crosses a border, a Customs declaration block appears: "This parcel crosses a border. Customs needs an HS code and country of origin for every item."
5. Complete the declaration
Fill in the block; the fields start from your Customs defaults.
- Contents, If it can't be delivered, and (when Contents is Other) Describe the contents.
- Signed by (legal name).
- For each item: HS code (6 to 10 digits, dots allowed) and Origin (two letters). They are filled from the variant or product when set.
- Duties and taxes: Recipient pays on arrival (DDU) or I pay in advance (DDP).
- ITN: only for shipments from the US with a declared value of USD 2,500 or more; enter the AES ITN (X followed by 14 digits).
- Use store defaults for items with no HS code or origin: tick this to fill gaps from your Customs defaults. It is never applied silently.
6. Fix anything it flags
Get rates stays disabled until every item has an HS code and origin, and a message names the item or the problem (for example "Describe the contents of the parcel"). Fix it on the card, or set the missing values once in Settings > Shipping and delivery > Customs defaults and tick Use store defaults.
7. Get rates and buy the label
Select Get rates, choose a rate and select Buy label. Changing anything in the declaration or the items after getting rates means you must select Get rates again, so the label always prices what you see.
8. Check what was sent
Your store builds the declaration from the order itself: each item's description is the product title, with its quantity, net weight, declared value (the order price times quantity, or your Minimum item value for a 0.00 item), HS code and country of origin. You can only choose the contents type, non-delivery option, explanation, signer, duties and taxes, ITN and HS/origin overrides. After purchase the label shows "Customs: Gift, 2 items, signed by …" and a Commercial invoice link when Shippo returns one.
Completion checklist
- Every item has an HS code and origin, or you ticked Use store defaults.
- The Ship from location has a country and full address.
- You set the Signer to your legal name if it differs from your store name.
- You re-ran Get rates after changing the declaration.
Troubleshooting
The Customs declaration section does not show.
The destination country is the same as the country of the Ship from location, or the pair is treated as domestic (EU to EU, or the US and its territories). Check the Ship from location's country in Settings > Locations.
Get rates is disabled and a message names an item.
That item has no HS code or country of origin. Fill them in on the card, on the variant, or tick Use store defaults after saving Customs defaults.
The label says an item has a price of 0.00.
Customs needs a value for every item. Set a Minimum item value in Customs defaults (default 1.00) so free or gift items are declared at that amount per unit; 0 blocks the label instead.
A US shipment asks for an ITN.
US exports declared at USD 2,500 or more need an AES ITN. Enter it in the ITN field; below that amount no ITN is needed.
Does this work for ShipStation labels?
No. Customs declarations are only built for Shippo labels; ShipStation labels and exports do not carry the HS code or origin, so enter customs details in ShipStation.
Set your store's tax rate
Set one tax rate for your store, and decide whether it's included in your prices and whether shipping is taxed.
Illustrated guide: lulu.us.com/help/configure-your-tax-rate
Before you startTax is your responsibility — Lulu calculates and charges tax on orders using the rate you enter, but doesn't remit or file taxes on your behalf. Check your local tax obligations before configuring this. This rate is your store's base/fallback rate — add country and region registrations under Settings > Taxes and duties for per-destination rates (see register-where-you-collect-tax).
1. Open Taxes and duties
Go to Settings > Taxes and duties.
2. Enter your tax rate
In the Tax calculation card, enter your Tax rate as a percentage, for example 8 for 8%. It must be between 0 and 100. This is your store's base rate: while you haven't registered any country or region under Settings > Taxes and duties, it applies to every taxable product line, whatever the customer's address. Once you add your first registration there, it becomes the fallback rate for any country you haven't set a specific rate for — see register-where-you-collect-tax and set-tax-rates-by-country-and-region.
3. Choose whether tax is included in prices
Tick Include sales tax in product price and shipping rate if the prices you show already include tax (some countries require this). Leave it unticked to add tax on top of your prices at checkout.
4. Decide whether shipping is taxed
Tick Charge tax on shipping rates if your region taxes the shipping charge as well as the products. When it's ticked, shipping and any per-product handling fees are taxed too.
5. Decide on digital goods
The Charge VAT on digital goods box is saved for future use, but checkout doesn't use it today. Digital products, like any other product, are taxed according to their own Charge tax on this product setting. If a digital product shouldn't be taxed, untick Charge tax on that product.
6. Save
Click Save. The rate applies to orders placed after you save. Orders that already exist keep the tax they were charged.
Completion checklist
- Enter your store's tax rate as a percentage (0 to 100)
- Decide whether that rate is already included in your prices
- Decide whether shipping charges are taxed
- Untick Charge tax on any product (digital or physical) that shouldn't be taxed
- Save, then check the Taxes report under Analytics > Reports to confirm collection looks right
Troubleshooting
Can I set different tax rates for different countries or states?
Yes. Go to Settings > Taxes and duties > Where you collect tax and add the countries and states you're registered in, each with its own rate — see set-tax-rates-by-country-and-region and register-where-you-collect-tax. Until you add any, this one rate applies everywhere.
How is tax calculated when my price already includes it?
With Include sales tax in product price and shipping rate turned on, Lulu backs the tax portion out of the tax-inclusive total (Tax = Rate × Price ÷ (1 + Rate)) rather than adding it on top, so the customer's total doesn't change.
What does the Duties and import taxes card do?
Nothing yet — it's shown as "Not set up" for reference only. Lulu doesn't currently collect duties or import taxes at checkout.
Where can I see how much tax I've collected?
Go to Analytics > Reports and open the Taxes report (in the Finance category). It shows a daily breakdown of the tax collected.
I ticked Charge VAT on digital goods, but my digital products are taxed the same as before.
That box is saved, but checkout doesn't use it yet. Tax on any product, digital or not, is decided by its own Charge tax on this product setting and your store's tax rate.
Exempt specific products, companies, and customers from tax
Turn off tax on an individual product, or exempt a B2B company's orders entirely.
Illustrated guide: lulu.us.com/help/tax-exemptions-for-products-and-customers
Before you startThis article covers exemptions on top of the store-wide tax rate set in Settings > Taxes and duties.
1. Turn off tax on a specific product
Open the product from Products. In its pricing details, expand the Charge tax chip and untick Charge tax on this product. While it's ticked, the product is taxed at your store's tax rate.
2. Exempt a B2B company
Go to Customers > Companies, open the company, and tick This company is tax exempt (you can also tick it when you create the company). Orders the company's buyers place through your online store checkout are charged no tax, and the company shows a Tax exempt badge.
3. Mark an individual customer tax-exempt
Open the customer from Customers. In the Tax details card, untick Collect tax. The card then says taxes won't be collected on this customer's orders. This exemption is honoured at your online checkout, but only when that customer is signed in to their own account — a guest who simply types this customer's email is still charged tax, so you can't rely on it for a customer who always checks out as a guest. It also doesn't apply on a store whose prices include tax (the checkout still shows "Tax included" on those). At the Point of Sale register, the customer is labelled Tax exempt in the customer list, but tax still isn't removed automatically — the cashier needs to turn on Tax exempt for the sale (see the next step).
4. Exempt a sale at the register (POS)
At the Point of Sale register, a cashier with permission to edit taxes can tap Tax exempt on the cart, which removes tax from that sale. POS settings has a Tax-exempt reasons list you can keep (for example Resale), but the register doesn't ask for or record a reason on the sale today.
5. Know when the customer exemption doesn't apply
A signed-in customer's exemption is skipped — the order is taxed normally — on a store that prices with tax included, because stripping included tax out for one buyer isn't supported yet. The order page labels an exempt order "Tax exempt (customer)" or "Tax exempt (company)" so you can tell which rule exempted it.
Completion checklist
- Untick "Charge tax on this product" for products that shouldn't be taxed
- Mark a B2B company tax exempt if its online orders should never be taxed
- Remember a customer's own "Collect tax" exemption only applies online when they're signed in, and never on a tax-inclusive store
- Use the cart's Tax exempt option at POS for one-off exemptions
Troubleshooting
I marked a customer tax-exempt but their online order was still taxed.
Check they were actually signed in at checkout — a guest who just types that customer's email is still taxed. Also check your Taxes and duties setting: a customer exemption doesn't apply on a store whose prices include tax. A B2B company's exemption, by contrast, applies whether its buyer is signed in or not. At the POS register, the cashier taps Tax exempt on the sale.
Does turning off tax on a product affect shipping tax?
No. Charge tax on this product only affects that product line. Whether shipping is taxed is set separately with Charge tax on shipping rates in Settings > Taxes and duties.
Can I require a resale certificate before exempting a company?
No. Tax exemption on a company or customer is a simple on/off setting. There's no certificate upload, expiry date or verification step.
The order page shows "Tax exempt (customer)" — what does that mean?
It means the signed-in customer's own "Collect tax" exemption removed the tax, as opposed to "Tax exempt (company)", which means a tax-exempt B2B company's rule applied instead.
Set tax rates by country and region
Charge the right rate for each country and state once you're registered there, instead of one flat rate everywhere.
Illustrated guide: lulu.us.com/help/set-tax-rates-by-country-and-region
Before you startThis builds on your store's base tax rate (see configure-your-tax-rate). Once you add your first country or region, Lulu switches from one flat rate to charging destinations only where you're registered — see register-where-you-collect-tax for the registration rule itself.
1. Open Where you collect tax
Go to Settings > Taxes and duties. Before you add anything, the pane says "You charge X% on every order, wherever it ships" — that's your store-wide rate from configure-your-tax-rate, still in effect.
2. Add a country or region
Click Add country or region, choose A country or state, pick a Country, and optionally a State or province (in the US you register for sales tax state by state). Enter a Tax name (prefilled, for example VAT or GST) and a Country rate — Lulu suggests a standard rate for many countries, but you're responsible for the rate you charge. Click Add.
3. See your home country added automatically
The first time you add any registration, your store's own home country (and, in the US, home state) is added too at today's store-wide rate, so orders shipping there keep paying what they always have.
4. Add a state or province rate
Inside a country's group, click Add rate, choose Rate for the country or a state / province, pick the region under Applies in, and enter a Tax name and Rate.
5. Choose how a region rate combines with the country rate
When a region already has a country-level default, pick how they combine: Charge both (for example GST + PST), Charge this instead (for example HST replacing GST), or Charge this on top of the country tax (compounded).
6. Edit, delete, or remove
Use Edit or Delete on a rate row to change or remove it. Use Remove next to a registration to stop collecting there — its rates are kept if you register again, and orders already placed aren't changed.
Completion checklist
- Add a country or state for every place you're actually registered to collect tax
- Check your home country/state was added automatically at your old store-wide rate
- Decide how a state/province rate combines with its country rate: add, replace, or compound
- Remember changes apply to new checkouts only — orders already placed keep the tax they were charged
Troubleshooting
I added Germany, but a customer checking out to France isn't charged tax.
You're only registered in Germany. Add France separately, or register for the EU-wide One-Stop Shop (OSS) if you sell across the EU — see register-where-you-collect-tax.
I set a California state rate but the total looks wrong.
Check how it's set to combine with the country-level US rate: Charge both adds the two rates, Charge this instead replaces the country rate, and Charge this on top of the country tax compounds on it.
Will adding a country change tax on past orders?
No. Orders already placed keep exactly the tax they were charged, even if you edit or remove the rate afterwards.
Register where you collect tax (including EU OSS and IOSS)
Add the countries, states, and EU schemes you're registered in — Lulu charges tax only where you're registered, and nothing anywhere else.
Illustrated guide: lulu.us.com/help/register-where-you-collect-tax
Before you startGo to Settings > Taxes and duties. The rule shown at the top of the page: "Customers pay tax for the place their order ships to — only where you're registered to collect it. Pickup and digital orders use your store's address."
1. Add a single country or state
Click Add country or region, keep A country or state selected, pick the Country (and a State or province if you only collect there), and optionally a Tax registration number. Click Add.
2. Register for the EU instead (OSS or IOSS)
Click Add country or region and choose European Union (OSS / IOSS). Pick a scheme: One-Stop Shop (OSS) for sales to EU consumers, or Import One-Stop Shop (IOSS) for imports into the EU. Add an optional tax registration number and click Add. This one registration covers every EU member state.
3. Add a rate for each EU country you actually sell to
An OSS/IOSS registration alone doesn't set any rates. If a member state has no rate yet, a banner lists it: "No rate yet for [country] — orders there charge 0% until you add one." Add a country rate for each one you sell to (see set-tax-rates-by-country-and-region).
4. Know what "not registered" means
A country with no registration and no EU cover shows Not collecting, and new orders shipping there are charged no tax at all — not your old store-wide rate. If you remove your only registration, a warning says so before you confirm.
5. Watch for the home-region warning
If your default location's state or province isn't a recognised US state or Canadian province, a banner explains Lulu can't register just your home state yet, and asks you to fix it under Settings > Locations first.
Completion checklist
- Register every country or state you collect tax in — unregistered destinations are charged nothing
- Use the EU OSS/IOSS registration once instead of 27 separate country registrations, if you qualify
- Still add a rate for each EU country you actually sell to — OSS/IOSS alone sets no rates
- Fix your default location's state/province first if the home-region warning appears
Troubleshooting
What's the difference between OSS and IOSS?
One-Stop Shop (OSS) is for sales to EU consumers; Import One-Stop Shop (IOSS) is for goods imported into the EU. Pick the scheme that matches how you sell.
I registered for OSS but orders to France still show 0% tax.
OSS covers every EU country for registration purposes, but each country still needs its own rate row added before tax is charged there.
I removed my last registration by mistake — is anything lost?
No new tax is charged on new orders until you register again, but nothing about past orders changes, and your old rates come back if you register the same country again.
Add tax overrides for a collection or for shipping
Charge a different rate — or exempt it entirely — on a collection of products or on shipping, instead of the usual country or region rate.
Illustrated guide: lulu.us.com/help/add-tax-overrides-for-collections-and-shipping
Before you startYou need at least one country added under Settings > Taxes and duties before you can add an override for it (see register-where-you-collect-tax).
1. Open the country's rates
Go to Settings > Taxes and duties, find the country you want to override, and click Add rate.
2. Override a collection
Choose Override for a collection (for example, reduced-rate food or books). Pick Applies in (the whole country or a state/province) and the Collection. Products in this collection use this rate instead of the default ones — enter 0% to exempt them completely. Enter a Tax name and Rate.
3. Set a priority for overlapping collections
If a product can be in more than one overridden collection, set Priority (-100 to 100): the higher priority wins, and a tie goes to the lower rate.
4. Override shipping instead
Choose Override for shipping to set the rate charged on shipping (and handling) for that country or region, replacing whatever the goods rate would otherwise apply.
5. Save and check the rates table
The rate shows under that country with Override · [collection name] or Shipping override under Applies to. New checkouts use it right away; orders already placed keep the tax they were charged.
Completion checklist
- Use a 0% collection override to exempt a category of products in a country
- Set Priority when a product could match more than one overridden collection
- Override shipping separately — a collection override never changes the shipping rate
Troubleshooting
A product is in two overridden collections — which rate applies?
The override with the higher Priority wins; if priorities are equal, the lower rate applies.
Does a collection override also change the tax on shipping?
No. Shipping has its own separate override — add one under Override for shipping if you need a different shipping rate.
I moved a product into an exempt collection — does an order placed yesterday get recalculated?
No, past orders keep what they were charged. Collection membership is read at the moment of each new checkout, so only orders placed after the move use the new rate.
Show tax-included prices for a market
Keep one constant shelf price across every destination in a market by turning on tax-inclusive pricing, instead of adding tax on top at checkout.
Illustrated guide: lulu.us.com/help/show-prices-with-tax-included-per-market
Before you startThis is a per-market setting, so set it up for each market separately where your local rules require tax-inclusive pricing.
1. Open the market's Taxes settings
Go to Markets, open the market (for example a German market), and open its Taxes settings.
2. Turn on Prices include tax
With it on, the price a shopper in that market sees doesn't change by destination — the tax portion is backed out of that same price instead of added on top. The same €120.00 product shows tax of 19.16 in Germany and 20.00 in France, but the shopper pays 120.00 either way.
3. Decide whether shipping is taxed too
The same Taxes settings for the market also control whether shipping is taxed there, same as the store-wide Charge tax on shipping rates setting.
4. Check what shoppers see
The product page and cart show a short note such as "Prices include VAT." or "incl. VAT" for the market's browsing country; checkout labels the tax row with the named rate that applies (for example "VAT 19%").
5. Know what happens where you don't collect
In a country you're not registered in, the shopper still pays the same shelf price and no tax is recorded — the cart's Estimated taxes row reads "Not charged here" rather than a blank line.
Completion checklist
- Turn this on per market where shoppers must see one tax-included price regardless of destination
- Check the product and cart pages show the "Prices include..." note for that market
- Remember your net income still varies by destination, even though the shelf price doesn't
Troubleshooting
The price looks identical in two countries, but I'm keeping less of it in one.
That's expected with tax-included pricing: the shelf price stays constant and the tax backed out of it varies by the destination's rate, so your net varies even though the shopper's total doesn't.
I turned this on, and now a country I'm not registered in shows a price with no tax — is that right?
Yes. Where you're not registered, no tax is charged or recorded; the shopper simply pays the same shelf price as everyone else in that market.
Is this the same as Shopify's "dynamic tax-inclusive pricing"?
Close to it. Prices include tax on its own keeps the shopper's total constant. To keep your net price constant instead, tick Include or exclude tax based on your customer's country in the same Taxes popover — see Keep your net price the same in every country.
Keep your net price the same in every country (dynamic tax-inclusive pricing)
Let each customer pay your price before tax plus their own country's tax, so you keep the same amount in every country even though your prices include tax.
Illustrated guide: lulu.us.com/help/keep-net-price-constant-dynamic-tax-inclusive-pricing
Before you startThis is a per-market setting and it is off until you tick it. It needs the market's prices to include tax, taxes calculated by destination, and a tax registration with a rate for your home country.
1. Understand what it does
The price you enter is the tax-inclusive price in your home country. For everyone else, Lulu works out your price before tax and adds the customer's own country tax to it. Example: you list a product at $24.00 and your home tax is 10 %. Your price before tax is $21.82. A customer in a country where you charge 19 % pays $25.96 (tax $4.14 included). A customer in a country where you don't collect tax pays $21.82 with no tax. A customer in your home country still pays $24.00.
2. Check the prerequisites
Prices must include tax for the market (Markets > the market > Taxes and duties > Prices include tax, or the store-wide setting). Taxes must be calculated by destination. You need a tax registration for your home country with a rate above 0 % (Settings > Taxes and duties), and an address on your default location (Settings > Locations) so Lulu knows your home country.
3. Open the market's Taxes popover
Go to Markets, open the market and open its Taxes settings.
4. Tick the option
Tick Include or exclude tax based on your customer's country and save. If the checkbox is greyed out, read the red message under it: it tells you whether you need to add a home-country registration, add an address to your default location, or set a home rate above 0 %. It is also disabled until the market's prices include tax. You can always untick it.
5. Know what is and isn't re-priced
Taxable product lines are re-priced, rounded once per unit. Gift cards, shipping, handling, tips, products that aren't taxable and prices from a B2B company price list are not changed. A B2B company that is tax exempt pays your price before tax. Tax overrides (reduced rates for specific products) don't apply while this is on: every product is taxed at the destination's default rate. Discounts, deposits on pre-orders and free-shipping thresholds all use the price the customer actually pays.
6. Check what shoppers see
On product pages, collection pages, search, the cart and the other shop listings, prices follow the shopper's browsing country. At checkout the price follows the shipping address (the pickup location for pickup, your home country for digital orders). The order, invoice and refunds always use the charged numbers.
7. Know the limits
These show your listed prices instead: Point of Sale, draft orders, subscription renewals, marketplace seller carts, and carts and product feeds built for AI agents.
Completion checklist
- Tick the option only on markets whose prices include tax
- Add a home-country registration with a rate and an address on your default location first
- Check a test order to a country with a different rate and to one where you don't collect
- Remember POS, draft orders, subscription renewals, marketplace carts and AI-agent carts use listed prices
Troubleshooting
The checkbox is greyed out.
Either the market's prices don't include tax, or Lulu has no usable home tax rate. Read the red message under the checkbox: add a home-country registration with a rate above 0 % in Settings > Taxes and duties, or add an address to your default location in Settings > Locations.
A customer in my home country pays exactly the listed price. Is that right?
Yes. Your listed price is the tax-inclusive price at home, so a shipping address in your home country is never re-priced.
Why is my net a cent off the price before tax?
The price is rounded once per unit and the tax once per line, so your net is within one cent of the listed price divided by your home tax multiplier.
I changed the setting while a customer was checking out.
Turning it on or off counts as a tax change: the checkout asks the customer to review the new total, and a card or wallet order already sized keeps the pricing it was sized with.
Read the tax lines on an order, invoice, and confirmation email
See exactly which tax (VAT, GST, state tax…) was charged and at what rate, named the same way on the order page, the invoice, the customer's order status page, and the confirmation email.
Illustrated guide: lulu.us.com/help/read-tax-lines-on-orders-and-invoices
Before you startThis applies once you've registered anywhere under Settings > Taxes and duties — a store still on its one store-wide rate shows a single "Tax" line instead.
1. Check the order page
Open the order. The Payment card lists each tax charged by name and rate — for example "VAT 19%", or two separate lines like "GST 5%" and "PST 7%" when both apply to the same destination.
2. Check the printed invoice
Use More actions > Print invoice — the same named lines appear there.
3. Check the customer's own order page
The storefront order status page the customer sees shows the identical named lines.
4. Check the confirmation email
The order confirmation email shows the same named rows (or, if you've customized the template, wherever you've placed the {{ tax_lines }} placeholder).
5. Know when you'll see a single "Tax" line instead
An order placed while your store was on its one store-wide rate (before you added any country or region), or one placed through a path that still uses the store-wide rate (like a marketplace seller order or a counter sale), keeps one plain "Tax" row instead of named lines.
6. Remember tax lines never change after the fact
Editing a rate, removing a registration, or refunding part of an order never rewrites that order's original tax lines — a refund records its own amount separately, and the lines stay exactly as the customer was charged.
Completion checklist
- Check the order page's Payment card for named tax lines like "VAT 19%" or "GST 5%"
- Confirm the same lines show on the printed invoice and the customer's order status page
- Remember an order placed on your old store-wide rate still shows a single plain "Tax" line
Troubleshooting
An old order only shows one plain "Tax" line, not a named one.
That's expected for any order placed before you added your first country or region under Settings > Taxes and duties, or for one priced on the store-wide rate through a path that doesn't use destination tax yet (marketplace seller orders, counter sales).
Can I see total tax collected by country?
Analytics > Reports > Taxes shows your overall tax collected; a breakdown by jurisdiction isn't built yet.
I changed a rate — will past orders update to the new amount?
No. Rate changes only affect checkouts placed after the change; every order keeps exactly the tax lines it was charged.
Open your store, add apps and themes, and pay for each one
A complete walkthrough for store owners: sign up and pay for your package, sign in, install apps and choose app plans, buy and publish a theme, and find every charge under Settings > Billing.
Illustrated guide: lulu.us.com/help/guide-store-owner-apps-themes-payments
Before you startYou pay for three kinds of things in Lulu, and each one is paid separately: your package (Basic $20, Grow $50 or Advanced $290 a month in USD, or Plus from $1,950 a month by agreement), the plan of each app you choose to pay for, and each premium theme you buy. There is no free package: the first billing cycle is paid on a secure payment page during signup, and your store is created only when that payment goes through. Apps and themes are optional; many apps have a free plan and every theme can be tried free before you buy it. All prices are in USD. Have a card ready and about 15 minutes.
1. Start your signup and create your account
Go to lulu.us.com and click "Get started" (or choose a package on the Pricing page). The signup form has three steps shown at the top: 01 Account, 02 Your store and 03 Package. On the first step either click "Continue with Google", or type your Email address and a Password of 8 to 72 characters (click "Show" to check what you typed). Then click "Continue →".
- Use an email address you can open: your welcome email and receipts go there.
- Already have a store? Click "Log in →" at the bottom of the form instead.
2. Name your store and choose its address
Type your Store name (at least 2 characters). The Store address is filled in for you from the name and ends in .lulu.us.com; you can change it, using 3 to 40 lowercase letters, numbers and hyphens. Wait until the form says "✓ This store address is available.", then click "Continue →". Use "← Back to account details" if you need to change your email.
- The address is only your free web address. You can connect your own domain later under Settings > Domains.
- If it says "This address is unavailable. Try another name.", change a word or add a hyphen.
3. Choose your package
On step 03 Package choose Monthly or Yearly (yearly saves up to 15%), then click the package you want. Each card shows the price, the number of staff accounts and the platform fee: Basic $20/mo (2 staff, 1.5% fee), Grow $50/mo (5 staff, 0.8% fee), Advanced $290/mo (15 staff, 0.5% fee). On Yearly the cards show the monthly equivalent and the total per year (Basic $204, Grow $540, Advanced $3,000). Plus (from $1,950/mo) is arranged with the team: its card says "Talk to us →" and opens the contact form. When a package is selected, click "Continue to payment ↗".
- You can upgrade or downgrade later under Settings > Billing, so pick what fits today.
- The platform fee is a percentage of your sales; your payment provider's own processing fee is separate.
4. Pay for the first billing cycle
The button changes to "Opening secure payment…" and you are taken to the secure payment page of the platform's card payment provider. It shows the package and the amount for the first cycle. Enter your card details there and confirm. Lulu never sees or stores your card number. When the payment succeeds you come back to the signup page, which shows "Payment received — opening your store…" and then "Your store is ready. Opening…", and your new admin opens.
- If you close the payment page or the payment fails, the form says "Payment not completed" and that nothing was charged. Click "Try payment again". Your email, store name and address are kept; you may be asked to type your password again.
- If your address was taken by someone else while you were paying, you get a close variation and the page tells you the new address.
- No payment means no store: nothing is created until the first cycle is paid.
5. Check what you receive
Two emails arrive. "Welcome to Lulu — your store name is ready" contains the "Open your admin" button, your store's web address, the storefront password and a shareable preview link. "Your Lulu receipt" confirms the package, the amount, the billing period and the payment reference. Your store starts in development: visitors see a password page until you go live, so you can build in private.
- Keep the receipt; the same bill is listed later under Settings > Billing > Past bills.
- You can see or change the storefront password under Online Store > Preferences.
6. Sign in to your admin
Go to admin.lulu.us.com (or click "Login" on lulu.us.com) and sign in with the email and password you chose, or with Google if you signed up with Google. Every admin page lives under admin.lulu.us.com/store/your-address/ followed by the page, for example admin.lulu.us.com/store/your-address/settings. The Home page shows a "Set up your store" guide that ends with "Go live".
- Bookmark admin.lulu.us.com/store/your-address to come straight back.
- If you manage more than one store, check the store name in Settings before you pay for anything.
7. Open the App Store
In the sidebar click "Apps", then click "Lulu App Store" at the top right (while no app is installed, the sidebar also shows "+ Add apps"). Search at the top or open a category such as Selling products or Marketing and conversion. Each app card shows its maker, a short description and its price label: "Free plan available", "Free trial available" or "Free to install".
- "Built for Lulu" and "Built by Lulu" mark apps made and supported by Lulu.
- "Your apps" at the top takes you back to the apps you have installed.
8. Read the app's listing and compare its plans
Open an app. The card on the left shows Pricing, Rating and Developer, a badge that says what kind of app it is (for example "Built by Lulu" or "Built-in feature") and the "Install" button. Scroll to Pricing to compare the plans: each plan card shows its USD price per month, its free-trial length (for example "14-day free trial") and its features. Features marked "Coming soon" are not available yet, so do not pay for a plan because of them. Read "What this app does in your store" to see exactly what you get.
- App plans are billed in USD for each period: 30 days, or 365 days on an annual plan.
- If an app is made by another company, the listing says that company may bill you separately for its own service.
9. Install the app and check what it can access
Click "Install". Nothing is added yet: a confirmation titled "Install" plus the app's name opens first. Under "This app will be able to:" it lists the store data the app can view or edit (or says it does not request access), under "Requirements" what you need to do or connect, and under "What it costs" the price and any trial. Click "Install" to add the app, or "Cancel" to leave without changes.
- After installing, the listing shows "Installed" with "Open app" and "Uninstall", and the app appears under Apps in the sidebar.
- Some apps also need to be switched on in the theme editor (Online Store > Customize); the Requirements list tells you.
10. Choose an app plan: free, free trial or development stores only
On the installed app's listing, go to Pricing and use the button on the plan you want. "Choose plan" picks a free plan straight away, or opens payment for a paid plan. "Start free trial" starts a paid plan free for the days shown, without a card; you get a trial only the first time you choose a paid plan of that app. A free plan marked "Development stores only" is free only while your store is still in development (before you go live); once your store is live the card says "Your store is live, so this free plan is no longer available. Choose a paid plan." The plan you are on is marked "Current plan", and a banner above the plans shows its status, for example "Active" with the renewal date or "Trialing until" a date.
- A paid plan starts the app's normal free trial (usually 14 days), then you pay for it. This happens whether or not your store is live.
- An app labelled "Free plan available" has a free plan you can keep after going live.
- An app labelled "Free to install" usually has a development-only free plan: budget for a paid plan when you launch.
11. Pay for an app plan
App plans are never charged to your card automatically. When a trial is running or a payment is due, the banner and the current plan show "Pay now" with the amount; after paying, the same button reads "Renew now" so you can pay the next period early. Click it and pay in the secure payment window. When it finishes you see "Payment received — your plan is active". If you close the window first you see "Payment window closed — your plan is unchanged until the payment completes." You get reminder emails before a trial or period ends.
- If a period ends unpaid, the plan shows "Past due" and the app is paused ("Suspended") 3 days later until you pay. Your settings are kept.
- If an app's payment is due when you go live, the Go live page (Home > Go live) lists it under "Paid apps" with "Total due" and a "Pay … for apps" button, charged one app at a time. An app whose free trial is still running is not charged when you go live: it bills when the trial ends.
12. Find your apps afterwards
Click "Apps" in the sidebar. The Installed tab lists each app with its Developer, Pricing, Plan (status and renewal date) and Status, with "Open", "Manage plan" and "Uninstall". "Open" goes to the app's own pages, "Manage plan" to its plan cards. Paid app plans are also listed under Settings > Billing > App subscriptions.
- To stop paying for an app, open its listing and click "Cancel plan" under Pricing: you keep access until the end of the period you paid for, then the app is paused.
- "Uninstall" removes the app from your store; check the listing for what happens to its data.
13. Find a theme in the Theme Store
In the sidebar click "Online Store". Next to "Draft themes" click "Browse themes" to open the Theme Store inside your admin (or "Visit Theme Store" for the public Theme Store site). Filter by Price (Free or Paid), Release, Made by, Industry, Style and Features, and use Sort to order by price or name. Each card shows the theme name, its maker and its price or "Free".
- Free themes made by Lulu are marked "Built for Lulu".
- "Your themes" at the top returns to Online Store.
14. Preview a theme with your own store
On a theme card or a theme's page click "View demo". The theme opens full screen using your store's name. Switch between desktop and mobile with the buttons at the top, or expand the preview. Click "Details" to go back to the theme's page, or "Try theme" to add it to your themes as a draft. Trying a theme is always free, including premium themes.
15. Buy a premium theme
A premium theme's page shows "One-time purchase", the price in USD and three buttons: "Buy" with the price, "Try theme" and "View demo". Click "Buy" and pay in the secure payment window. You pay once and get lifetime use of the theme on this store, with no renewal. After buying, the page shows "Owned". You can also try and customise a premium theme first and buy it only when you publish it.
- Each store buys its own copy: a theme bought for one store is not owned by your other stores.
- The page also shows who made the theme and that Lulu sells it and handles the invoice.
16. Customise and publish the theme
Back in Online Store, the theme you tried is listed under "Draft themes". Click "Edit theme" to change it without affecting your live store. When it is ready click "Publish" and confirm. A premium theme you have not bought shows "Buy to publish" with the price instead: click it to buy and publish in one go. The published theme moves to the top as "Live" and the previous theme moves to your drafts, so you can switch back at any time.
- While the banner says "In development: visitors need the password to access your store", only people with the password see your store. Use Home > Go live when you are ready to open it.
- Until you buy a premium theme, you can customise and preview it, but you can't edit its code: custom.js and head-snippets.html under Edit code are read-only, and GitHub sync is off. Custom CSS still works. Buy the theme to edit its code and to publish it.
- Your online store can hold up to 20 themes; delete drafts you no longer need.
17. See every charge and receipt in Settings > Billing
Click "Settings" at the bottom of the sidebar, then "Billing". Your package, your apps and your themes are billed separately and each has its own list: "Past bills" holds your package bills (first payment, renewals, upgrades), each with "Download"; "App subscriptions" lists every paid app with its plan, status, renewal date and "Manage plan"; "Charges" lists every app and theme payment with its date, amount and status. The page also shows your current package, Usage, "Current billing cycle" with the upcoming bill, and "Payment methods".
- A charge marked "Pending" has a "Check status" button; use it before paying again.
- Card payments appear on your bank statement under the platform's payment partner, with your Lulu reference.
18. Change or cancel your package, apps and themes
Under "Change package" click "Upgrade" or "Downgrade" next to another package. Upgrading applies straight away and charges only the difference for the days left in the cycle; downgrading takes effect on your renewal date. "Current billing cycle" shows the upcoming bill, and "Pay early" lets you pay it now. To stop using Lulu click "Cancel package": the confirmation explains that your package runs until the renewal date, the storefront then closes, you are not charged again (no refund for the rest of the cycle) and nothing is deleted for at least 90 days. Confirm with "Cancel at the end of the cycle", or keep it with "Keep my package"; you can undo the cancellation before that date.
- A package paid by card at signup is a card subscription that renews every 30 days (or every year) until you cancel it. When the Billing page shows your subscription, "Manage payment method or cancel" changes the card or cancels it.
- App plans are cancelled on each app's listing with "Cancel plan"; premium themes are one-time purchases and never renew.
Completion checklist
- You received the welcome email and the receipt for your first package payment.
- You can sign in at admin.lulu.us.com and your admin address is admin.lulu.us.com/store/your-address.
- Every app you installed appears under Apps with the plan you expect; paid plans show a renewal or trial end date.
- Apps with "Development stores only" free plans have a paid plan chosen before you go live.
- The theme you want is marked Live under Online Store; any premium theme shows "Owned".
- Settings > Billing lists your package bill under Past bills, your paid apps under App subscriptions and your app and theme payments under Charges.
Troubleshooting
The payment page closed or failed during signup. Was I charged, and is my store created?
If the signup page says "Payment not completed", nothing was charged and no store was created. Click "Try payment again". If it says "Still confirming your payment", the payment went through and the store opens shortly: check your email before paying again, and contact support with your email address if nothing arrives.
An app's free plan button says "Development stores only".
That free plan is only for stores that are still in development. Your store is live, so choose one of the paid plans; if you have never trialled that app, the paid plan starts with a free trial.
Publish says "Buy to publish" on a draft theme.
The draft is a premium theme you have not bought for this store. Click "Buy to publish" (or "Buy" on the theme's page in the Theme Store), complete the payment, then publish. You can keep customising the draft for free in the meantime.
A payment window says the payment could not start, or a charge stays Pending.
Nothing is switched until a payment completes. Under Settings > Billing > Charges click "Check status" on the pending line before paying again. If a payment window cannot start at all, contact support with your store address and what you were paying for.
I paid, but the package, app plan or theme still shows the old state.
Reload the page after a minute. For app and theme payments use "Check status" under Settings > Billing > Charges. If it still has not changed, send support your store address and the payment reference from your receipt; do not pay a second time.
What should I send support?
Send your store address, the page you were using, the steps you took and the exact message you saw. Include a screenshot with customer details hidden. Never send passwords, full card numbers or security codes.
Let customers save a card and control 3D Secure
For store owners: turn on saved cards at checkout, choose how many of a customer's first payments ask for 3D Secure, see what the shopper experiences, and find the cards saved on your own Lulu account under Settings > Billing.
Illustrated guide: lulu.us.com/help/guide-saved-cards-store-owner
Before you startSaved cards and merchant-controlled 3D Secure work only with Stripe today: if you take card payments through PayPal, PayHere, or another Sri Lankan gateway instead, your customers type their card details every time and none of this applies. You'll need your own Stripe keys added and card payments enabled in Settings > Payments. Nothing here needs code or an app.
1. Check which gateway you need: Stripe
Saved cards and the 3D Secure control only exist for the Stripe gateway. If your store takes cards through PayPal or a Sri Lankan gateway (PayHere and the others), customers are asked for their card on every order and there is nothing to turn on — those providers don't offer this today. If you haven't added Stripe yet, go to Settings > Payments, choose Stripe from the gateway list and add your publishable and secret keys first.
2. Turn saved cards on or off
In Settings > Payments, find the Stripe card and its "Saved cards and 3D Secure" section. Tick "Offer to save cards for future purchases" so a signed-in customer with a confirmed email can save their card at checkout; untick it and no card is ever saved from your store, and any saved-cards list your customers had disappears from their account (their card is not deleted from Stripe, just no longer shown or offered here).
- Turning it off doesn't affect a customer's card saved for a subscription-style purchase elsewhere on the platform — it only controls your own store's checkout.
3. Choose how many first payments ask for 3D Secure
"Ask 3D Secure on a customer's first N payments" counts a customer's successful payments at your store from 0. While they're under N, every payment is sent to the bank with a request for 3D Secure (a one-time code or a banking-app confirmation); once they pass N, 3D Secure is asked for only when the customer's bank or card network requires it. Enter 0 to never request it yourself and let Stripe decide on every payment.
- A returning customer who already passed N on a saved card isn't asked again just because you raise the number later.
- The most you can set is 10.
4. Know what the shopper sees
The "Save this card" box at checkout is unticked by default and only ever shown to a signed-in customer whose email is confirmed — a guest, or a customer who hasn't confirmed their email, never sees it and can't save a card. Stripe's own standard notice explains the card is being saved; we don't change or hide it. A card is only ever saved if the shopper ticks the box themselves before paying. Once they've saved a card, shoppers also have their own "Payment methods" page in their account, where they can add, edit, make primary or remove a card any time — not just at checkout.
5. Know that you never see the card number
A saved card is kept by Stripe against the customer's own account on your store, never on Lulu's servers and never visible to you: your admin and orders only ever show the card brand and the last 4 digits, the same as any other payment. If a customer disputes or needs a refund, you still use the normal Orders and Refunds tools — nothing about a saved card changes how you refund an order.
6. If the fields say "Set by the platform"
Lulu can enforce a single saved-cards policy across every store. When it does, your "Saved cards and 3D Secure" fields are greyed out with the note "Set by the platform": your store then uses the platform's own default for saving cards and for how many first payments ask for 3D Secure, and you can't change either until the platform administrator turns enforcement off again.
7. Find the cards Lulu itself has saved for you
This is separate from your customers' cards: it's the card Lulu saves when you pay your own bills (plan renewals, app plans, themes, top-ups). Go to Settings > Billing — a "Saved cards" block sits next to your current payment method, showing each card's brand, last 4 digits and expiry, with a "Default" tag on the one used automatically for renewals. Click "Manage cards" to add, replace or remove a card, or make a different one the default; it opens Stripe's own billing portal for your account.
- "No saved cards yet" simply means you haven't paid Lulu by card yet — the card you next pay with is saved automatically.
- Manage cards may refuse to remove the card an active plan or POS Pro subscription is billed to; add and set another card as default first.
8. Your own cards for platform bills
The Card wallet under Settings → Billing → Saved cards is where you manage every card Lulu can charge for your own bills — plan renewals, POS Pro, app plans, themes, domains and top-ups. It's completely separate from your customers' cards, which stay in their own Payment methods page that only they can see.
9. Add a card on Stripe's own setup page
Click "Add card". This opens Stripe's own secure page in a pop-up — there's no card field on Lulu itself, so your card number never touches our servers. The button reads "Waiting for the secure page…" while it loads. When you return, "Card added" confirms it; your very first card becomes your Primary card automatically.
10. Primary and Backup badges
Primary is the one card charged automatically for your live plan and POS Pro subscription renewals, and for your next one-off bill. Every other saved card gets a Backup badge with a number (Backup #1, #2, …) — the order they'd be tried if a renewal is declined and you've turned that on (see below). Open a backup card's ••• menu to "Make backup #1", "Move up" or "Move down".
11. Edit or remove a card
Open a card's ••• menu for "Edit" (nickname, name on card, expiry, billing address — never the card number: add the new card and remove the old one instead) or "Remove". You can't remove your only card while a subscription is active — add another card first. If the card is your Primary card and a subscription is live, you're asked to choose a new primary card before it can go.
12. "Not used for automatic payments"
A card shows this note when it isn't Primary and isn't set as any subscription's own default, so nothing would charge it automatically, including as a backup: "Not used for automatic payments. Make it primary, or add it again here, to allow that." Either make it Primary, or add the same card again through "Add card" so its consent is recorded.
13. Let backup cards cover a declined renewal
Tick "Use my backup cards if my primary card is declined" — off by default — to let Lulu try your backup cards, in order, when a plan or POS Pro renewal is declined on your Primary card. You're agreeing to: "I authorise Lulu to charge my backup cards, in the order shown, when my primary card is declined for a plan or POS Pro renewal. Each backup card is tried at most once per bill, and no more than 3 cards per bill. I can turn this off at any time." Only cards marked for automatic payments are tried, at most 3 per bill, and it stops the moment your bank asks you to confirm the payment yourself. You get an email if a backup card is charged, suggesting you make it your new Primary card. Turning the toggle off stops any further backup charge — a charge already sent to Stripe at that moment can still complete.
14. If a bill is charged to a different card set
If your plan or POS Pro subscription is billed to a card Lulu set up under a different Stripe customer record — most often on an older store — changing your Primary card here won't move it, and you'll see a note to contact support instead. Contact support to have the subscription rebound to your current card wallet.
15. Lulu never sees your card number
Card numbers are stored by Stripe, not by Lulu — your billing page only ever shows the brand and last 4 digits, the same as your customers see for theirs. You can save up to 10 cards; to change a card's number, add the new card and remove the old one.
16. See how many cards a customer has saved
On Admin → Customers → a customer's page, the Payment methods card shows "Saved cards: N" — how many cards that customer has saved for faster checkout at your store, kept in your own Stripe account. You can see the count but not the cards themselves; only the customer can add or remove them.
Completion checklist
- Stripe is the gateway you use for card payments (saved cards don't exist on other gateways).
- Settings > Payments shows the Offer to save cards checkbox and the 3D Secure number set the way you want, or "Set by the platform" if the platform enforces it.
- You understand a customer only sees the save-card box when signed in with a confirmed email, and only saves a card by ticking it themselves.
- You checked Settings > Billing > Saved cards for the card Lulu saves for your own bills, separate from your customers' cards.
Troubleshooting
A customer says they never see a "Save this card" box.
Check three things: "Offer to save cards for future purchases" is ticked in Settings > Payments, the customer is signed in (not a guest), and their email is confirmed. Any one of those missing hides the box.
The saved-cards fields are greyed out and say "Set by the platform".
The platform administrator has enforced a single policy for every store. Contact support if you need an exception; you can't change these two fields yourself while enforcement is on.
My store is in development mode. Can I try card payments?
Yes. Enter your provider's test keys and place test orders; no real money moves. Real cards are accepted once your store is live under Home > Go live, with your live keys.
Can I see or export a customer's card number?
No. Neither your admin nor Lulu ever stores or displays a full card number — only the brand and last 4 digits, exactly like any other order's payment method.
A saved card says "Not used for automatic payments".
That card isn't your Primary card and isn't set as a subscription's own default, so nothing charges it automatically — make it Primary, or add the same card again through "Add card", to fix it.
I turned on backup cards but nothing was charged when a renewal failed.
Check that you have at least one card with a Backup badge, that it isn't expired, and that the decline wasn't a bank request to confirm the payment yourself (3D Secure) — the fallback stops there and sends the normal payment-confirmation email instead.
Your monthly bill
For store owners: how the monthly bill brings your plan, app charges, POS Pro locations and transaction fees together into one payment every 30 days, where to see the next bill and its lines, and what to do if a payment needs your attention.
Illustrated guide: lulu.us.com/help/guide-merchant-monthly-bill
Before you startThis guide is for store owners, not shoppers. You need a store owner or manager account with access to Settings → Billing. Whether you have a monthly bill at all depends on how your store pays: stores on an auto-charged card plan or on Marx get one bill every 30 days; an annual plan gets a bill too, once a year on the bill date after its anniversary. Only a custom-priced store pays each charge on its own with no bill. If your store has no bill yet, the "Monthly bill" card does not appear on your Billing page.
1. Open Settings → Billing
Sign in to your store admin and go to Settings → Billing. If your store has a monthly bill, a "Monthly bill" card appears near the top, above the older plan and app cards. It tells you in one line how your card is charged: on a card plan, your primary card is charged automatically on the bill date; on Marx, you pay the link yourself on the bill date — nothing is charged automatically. The rest of this guide covers both; a note in each step says where they differ.
- It's one payment, on one date, for everything on your store that month — your plan, paid apps, POS Pro locations and transaction fees — not several separate charges.
- If you don't see this card, your store isn't on a monthly bill yet — your plan and any apps are still billed the old way.
2. Accept your billing terms
The first time your store is billed this way, and again if how billing works ever changes, you're asked to review and accept the current billing terms before a bill can be charged — a card-plan store sees this on the Monthly bill card itself; a Marx store isn't asked, since nothing is ever charged without you opening the bill link yourself. Accepting takes one click and covers every future bill until the terms change again.
- You can re-read the terms at any time — see the last step, "How your monthly bill works".
- A card-plan bill can't be charged until this is accepted; if one is waiting on you, the Billing page and an email both say so.
3. Check your next bill
The card header shows "Next bill <date>". Below it, "Next bill · <date> (estimate)" shows the running total for the current 30-day cycle, broken into lines you can check before you're charged: your plan, any paid apps or POS Pro locations renewing in this cycle, and transaction fees for the month that just closed. A few days before your bill date we also email you this same estimate as a courtesy — it isn't a charge notice, just a heads-up. The estimate updates as the cycle goes on and the final amount is only set on the bill date itself.
- Transaction fees for a month are added to the first bill after that month closes — so this month's fee usually shows up on next month's bill, not this one.
- A plan upgrade is prorated for the time left in your current term and added to your NEXT bill, not charged right away; a downgrade starts at your next term with no partial-period credit.
- An annual plan is charged in full on the next bill date after its yearly anniversary (up to 30 days later) and covers a further 365 days of service.
- If the estimate says it isn't available right now, try again in a minute; nothing is wrong with your account.
4. Look at the Bills table
The "Bills" table below lists every bill for your store, most recent first, with its cycle dates, total, and status. Click a bill number, or the "View" button, to open it: you'll see every line (grouped as Plan, Apps, POS Pro, Transaction fees, and Adjustments & credits), any credit or cashback applied, and every payment or refund recorded against it. From the table or the detail you can also open "Receipt" (a printable page) and "CSV" (every line as a spreadsheet).
- A bill still being put together shows as "Preparing" — its lines can still change until the bill date.
- "Pay now" only appears on a bill that needs payment (open, failed, or one we couldn't collect automatically).
5. Download a PDF invoice from Past bills
Further down Settings → Billing, the "Past bills" list is where you download a PDF invoice for any bill — the same grouped lines as the bill detail, ready to save or forward, with a PAID or DUE stamp and the amount that was actually charged. Click "Download" next to the bill you want.
- A PDF is available for any bill once it has a total — a "Preparing" bill has nothing to download yet.
- A refunded bill's PDF is stamped REFUNDED instead of PAID.
6. If a payment needs your attention
If your card is declined on your bill date, we email you right away, then again on day 3 and day 7 if it's still unpaid — those three reminder emails are all you get, though automatic retries can continue a little longer in the background. You can click "Pay now" on the bill yourself at any point. A few situations need something from you specifically, and we always tell you which one by email and on the Billing page: your bank may ask you to confirm the charge yourself (sometimes called 3-D Secure) before it will let it through; your store may have no working card on file to charge; or the billing terms may have changed since you last agreed to them. Each of those emails links straight to the thing to do — confirm the payment, add a card, or review and accept the terms — and once it's done, billing carries on as normal with no extra charge. A retry, including a backup-card attempt, collects the SAME bill — it's never a second charge. If nothing is resolved in time, the bill shows "couldn't be charged" at the top of the page and your store is paused until every outstanding bill is paid. (Marx: there's no card to decline or retry — you always pay by opening the bill link yourself. Your store can still be paused if a Marx bill goes unpaid long enough; it just never happens through a declined charge, so the confirm-payment, add-a-card and backup-card parts above don't apply.)
- The oldest unpaid bill is what decides whether your store is paused — pay that one first if you have more than one outstanding.
- Adding a new card does not by itself clear a pause; you still need to pay the unpaid bill.
- Once a paused store's bills are fully paid, it comes back online right away and you get a confirmation email with a receipt — there's nothing else to turn back on.
7. Cards on file and the backup-card option
Your saved cards live further down the Billing page, in the same place as always. If your store is on the monthly bill, a banner asks you to confirm backup cards for it (a separate agreement from the older one, because now a backup card can cover your plan, your apps and your transaction fees together, not just your plan). Turn on "Use my backup cards if my primary card is declined" to let us try them, in the order you choose, only when your primary card is declined and only for payments where your bank doesn't need to confirm anything first — you get an email whenever a backup card is used. You can replace your primary card at any time; the new card is used starting with your next charge, and nothing already billed changes.
- You can turn this off again at any time; nothing changes about your saved cards themselves.
- You can still remove any card except the last one on file while money is owed.
8. If you cancel your plan
Cancelling doesn't refund the period you've already paid for — your store keeps working normally until the end of it, then closes. Your final bill, covering whatever was still owed for that last period (including any transaction fees that only closed out after you cancelled), is issued and collected after your store closes, not before. You'll get an email either way: a receipt if it's already paid, or a "Pay your final bill" link if it still needs a payment.
- The final bill works exactly like any other — same grouped lines, same Receipt/CSV/PDF links.
- Once your final bill is settled, choosing a plan again starts a fresh billing cycle, not a reopening of the old one.
9. How your monthly bill works
Click "How your monthly bill works" at the bottom of the card to read the current terms in full — the same document you accepted in step 2, and the same text we send in your first bill email. Terms can be updated occasionally (for example, to cover a new kind of charge); if that happens and it affects your bill, you're asked to review and accept the current version again before that bill is charged.
Completion checklist
- The Monthly bill card shows a next bill date and an estimate broken into Plan / Apps / POS Pro / Transaction fees.
- The current billing terms are accepted — no card-plan bill is waiting on that.
- You can open a past bill and see its receipt and CSV, and download a PDF invoice from Past bills.
- You know which card (or cards) will be charged, and backup cards are confirmed if you want them used.
- No unpaid bill, confirmation request, or terms update is waiting for you at the top of the Billing page.
Troubleshooting
I don't see a Monthly bill card at all.
Your store isn't on a monthly bill. It may be on a custom price, or the feature simply hasn't been turned on for your store yet — your plan and apps are billed the way they always were. An annual plan DOES get a monthly-bill-style bill — once a year, on the next bill date after its anniversary.
This month's transaction fees aren't on this bill.
Fees for a month are only added once that month has fully closed, so they land on the next bill after it, not the one covering the same days you traded in.
I got an email asking me to confirm a payment.
Your bank needs extra verification before it will approve this specific charge (sometimes called 3-D Secure). Click "Confirm payment" in the email or on the bill — it only takes a moment. Once you confirm, this bill is paid.
I got an email asking me to add a card.
Your store doesn't have a working card on file, so the bill can't be charged automatically. Add a card from the email's link or from Settings → Billing to pay it and keep your store running.
I got an email about updated billing terms.
How billing works changed slightly since you last accepted the terms. Review and accept the current version from the email or the Billing page — nothing already billed changes, and this only affects charging your NEXT bill.
My store is paused even though I just paid.
Pay the oldest unpaid bill first — that's the one the pause is keyed to. If you have more than one unpaid bill, paying a newer one first doesn't lift the pause.
A plan upgrade I made isn't on this bill.
An upgrade's prorated cost is added to your NEXT bill, not this one — check the next bill's estimate on the Monthly bill card.
"Pay now" opened a window that then closed.
The bill updates once the payment is confirmed, even if the window closed early. Refresh the Billing page after a moment; contact support if the bill still shows unpaid and you believe you were charged.
Where do I download a PDF for a bill?
Past bills, further down Settings → Billing — click Download next to the bill. The Bills table above it has Receipt and CSV instead.
Billing says my store is billed through a reseller.
Your reseller (the partner who handed the store over to you) has prepaid your plan for a fixed term. Settings → Plan shows "Billed through" with their name, your plan and the date it is prepaid until. You still own your store and its data, and your plan isn't charged to you while the term runs. To change or cancel the plan, contact your reseller; a bigger plan than the one they paid for is billed to you directly — contact support to arrange it. Apps, themes and other extras are always billed to you. If the term ends and your reseller doesn't renew it, you are never billed automatically. You are told on day 3 after the term ended. From day 14 you can choose a plan and pay for it yourself on Settings → Plan or Settings → Billing. If nobody pays, your storefront is paused on day 30 and the store is closed on day 90. See "If your reseller does not renew your plan".
Settings → Plan says it is waiting for my reseller to pay.
Your reseller hasn't completed the payment for your prepaid plan yet. The plan starts as soon as they do. If they haven't paid by the date shown, you can choose and pay a plan yourself on the same page.
Choose what a partner can do in your store
For store owners: what a collaborator can do by default, how to tick extra permissions for one partner, how to turn exports on, what a collaborator can never do, and when access ends by itself.
Illustrated guide: lulu.us.com/help/guide-merchant-collaborator-permissions
Before you startYou need the store owner account, or a role with the "Manage users" permission. The partner must already have access: you approved their request, or you granted it from Onboarding partners → My requests. This works on every plan.
1. Know what a collaborator gets by default
A collaborator can work on themes, products, orders, apps, shipping and store settings. Since 20 November 2026 the default no longer includes four things.
- Not in the default: exporting customers, exporting orders, exporting a store backup, restoring a backup.
- Also off unless you turn it on: everything under Finance, and approving paid app charges.
- Still in the default: importing and exporting products, and the non-finance reports.
- This also applies to partners who had access before 20 November 2026.
2. Open the collaborator's access
Go to Settings → Users and open the Collaborators tab. Under "Collaborator access" each partner shows "Default access" or "Custom access · N permissions". Click "Edit access" next to the partner.
- The window is titled "Access for <name>".
3. Tick what this partner may do
Tick or untick the sections. Then click "Save access". You see "Collaborator access updated". The change applies the next time the partner uses your admin.
- Each partner has their own ticks. Changing one partner changes nobody else.
- If you are not the owner, you can only give permissions you hold yourself.
4. Turn exports on only when the job needs them
Exports hand over a copy of your data, so they are off until you tick them.
- Customer export: under Customers, tick "Export".
- Order export: under Orders, tick "Export".
- Store backup: under Store settings, tick "Export a store backup". The file contains the whole store, including the customer list.
- Without the matching export tick, a partner also can't create an API token or a webhook that reads your customers or orders.
- Untick them again when the job is done.
5. Know what a collaborator can never do
Some things can't be ticked for any collaborator: manage users or roles, change your plan, transfer or close the store, use Point of Sale, or restore a backup.
- If a partner asks for one of these, do it yourself.
6. Go back to the default
Open "Edit access" and click "Reset to default". The partner returns to the default set.
7. Know when access ends by itself
Access that is not used ends automatically. If a partner does not sign in to your store for 90 days, their access is removed and they are signed out.
- The partner gets a warning email after 75 days without signing in.
- You get an email when the access expires. Nothing else in your store changes.
- The Collaborators tab shows "Access ends <date> if not used" next to the partner.
- To give access back, open Settings → Users → Collaborators. The partner can also send a new request with your request code, which you approve like a first request.
- Access does not end when a partner order completes. Click "Remove access" when the work is finished.
8. If your request code is locked
After 5 wrong collaborator request codes for your store, new requests are paused for 60 minutes. You get an email titled "Collaborator requests are paused". Nobody got access.
- You don't need to do anything. Requests open again after 60 minutes.
- If you did not share your code with a partner, click "Generate new code" on the Collaborators tab. The old code stops working at once.
Completion checklist
- Each partner under "Collaborator access" shows the access you expect.
- Customer export, order export and store backup export are ticked only for partners who need them now.
- Partners whose work is finished have been removed with "Remove access".
Troubleshooting
My partner says they can no longer export customers or orders.
Exports left the default set on 20 November 2026. If the job needs them, open "Edit access" for that partner and tick "Export" under Customers or Orders.
There is no "Edit access" button next to a partner.
You need the "Manage users" permission. Ask the store owner if you don't have it.
I get "Collaborators can’t be given these permissions".
You ticked something a collaborator can never hold, such as managing users or changing the plan. Untick it and save again.
I get "You can only give someone permissions you have yourself".
You are not the owner and you ticked a permission your own role lacks. Ask the store owner to make the change.
A partner's access expired but they still work for me.
They did not sign in for 90 days. Give the access back under Settings → Users → Collaborators.
A partner can't create an API token or a webhook.
Tokens and webhooks that read customers or orders need the matching export tick. Tick "Export" under Customers or Orders for that partner, or create the token yourself.
See what your partner did: the Activity log
For store owners: open Settings → Activity to see which changes each collaborator made in your admin, when, and from where. Filter by person type and date.
Illustrated guide: lulu.us.com/help/guide-merchant-activity-log
Before you startYou must be signed in as the store owner. Nobody else can open the Activity page: not administrators, not staff, not collaborators.
1. Open Activity
In your store admin go to Settings and click "Activity" in the side menu. The page lists the changes collaborators made in your admin, newest first.
- The page says "Entries can’t be edited or deleted." That is true for everyone, including you and the partner.
2. Read an entry
Each row has four columns.
- "When": the date and time.
- "Who": the person's name and email, with a "Collaborator" badge and, below, the partner business they belong to.
- "What": the change in plain words, for example "Updated a product". A "Failed" badge marks an attempt that did not go through.
- "Details": the record that was changed and the admin action that was used. Where known, the IP address.
3. Choose whose activity to show
Use "Show" to switch between "Collaborators" (the default), "Your users" and "Everyone".
- "Your users" lists your own staff. Entries made by an app carry an "App" badge.
4. Pick a date range
Set "From" and "To" to narrow the list. "Clear dates" removes the range.
- The start date must be on or before the end date.
5. Move through the pages
Use "Previous" and "Next" under the table. The badge next to the title shows the number of entries.
6. Know what is and is not recorded
The log records changes: something created, updated or deleted in the admin. Sign-ins by a collaborator may also be listed.
- Looking at a page without changing anything is not recorded.
- The log shows what was changed, not the old and new values.
- If you see a change you did not expect, ask the partner first. Then tighten their access under Settings → Users → Collaborators → "Edit access", or click "Remove access".
Completion checklist
- Settings → Activity opens and shows "Collaborators" in the "Show" filter.
- You can find a partner's changes for the days they worked on your store.
Troubleshooting
I see "Only the store owner can see the activity log."
You are signed in with an account that is not the store owner. Ask the owner to look.
There is no "Activity" link in Settings.
The link shows for the store owner only.
The page says "No activity yet".
No collaborator has changed anything in your store yet. Changes made before 20 November 2026 may not be listed.
The page says "Nothing matches these filters".
Choose a wider date range, or set "Show" to "Everyone".
Can I delete an entry?
No. Entries can't be edited or deleted by anyone.
If your reseller does not renew your plan
For store owners whose plan is paid by a reseller: the notices you get, when you can pay for the plan yourself, the free month, when the storefront is paused and when the store is closed. You are never charged automatically.
Illustrated guide: lulu.us.com/help/guide-merchant-reseller-not-renewed
Before you startThis guide is for stores where Settings → Plan shows "Billed through <partner>". Your partner prepaid your plan for a fixed term, normally 12 months. Only the store owner can take the plan over. The days below count from the date your plan was paid until.
1. Know the timeline
You are never billed automatically. Nothing happens to your store without a notice first.
- While the term runs: nothing to do. Your partner gets renewal reminders 30, 14, 7 and 1 days before it ends. You do not.
- Day 0 to day 2 after the term ended: nothing changes and you see no notice.
- Day 3: first notice, by email and on Settings → Plan and Settings → Billing.
- Day 14: you can pay for the plan yourself.
- Day 30: your storefront is paused if nobody has paid.
- Day 90: your store is closed if nobody has paid.
2. Day 3: read the first notice
We email the store owner a notice about the plan. Settings → Plan and Settings → Billing show "Your <plan> plan has not been renewed yet." with the date it was paid until.
- Your store keeps working and you are not charged.
- The simplest fix is to ask your partner to renew it.
- The notice names the date from which you can pay for the plan yourself.
3. Day 14: pay for the plan yourself if you want to
We email you "Keep <store> running". The banner reads "You can now pay for your plan yourself." Choose a plan in the plan picker on the same page and pay. The price is the normal list price.
- When you pay for your first month, the next month is free.
- From then on the store is billed to you, and your partner no longer pays for it.
- You can still ask your partner to renew instead, until you pay.
- Only the store owner can do this. Other users see "Only the store owner can do this."
4. Day 30: the storefront is paused
If the plan is still unpaid, visitors see a "temporarily unavailable" page. We email you "<store>'s storefront is paused". The page shown to visitors does not mention billing or your partner.
- Your admin still works. You can sign in, manage the store and export your data.
- To bring the storefront back, choose a plan and pay, or ask your partner to renew. It comes back as soon as the plan is paid.
- The free month still applies when you pay.
5. Day 90: the store is closed
If the plan is still unpaid, the store is closed. Settings → Plan shows "This store is closed because its plan was not paid."
- You were not charged.
- Your data is kept. You can still download a backup of your store from the link in that notice.
- Choose a plan on the same page to reopen the store.
6. If your partner tells us they will not renew
A partner can say in advance that they will not renew. You then hear 30 days before the term ends: "<partner> will not renew your <plan> plan."
- Your plan stays paid until the date shown. The term is not shortened.
- From that date you can choose a plan and pay for it yourself. The free month applies.
- If nobody pays, the storefront is paused 30 days after the term ended and the store is closed 90 days after it ended.
7. What stays yours
You own the store and its data the whole time. Apps, themes and other extras were always billed to you and stay that way.
- You never see what your partner paid, and they never see your payments.
- After you take the plan over, your partner keeps collaborator access until you remove it under Settings → Users → Collaborators.
Completion checklist
- You know the date your plan is paid until. It is on Settings → Plan.
- The store owner's email address is one you read. All notices go there.
- You have decided who pays next: your partner, or you.
Troubleshooting
Will my card be charged if my reseller doesn't pay?
No. You are never charged automatically. You pay only if you choose a plan yourself.
I want to pay myself before day 14.
The plan picker opens on day 14 after the term ended. Until then, ask your partner to renew. If your partner told us they will not renew, it opens on the day the term ends.
I can't see the plan picker but my colleague got the email.
Only the store owner can take the plan over. Sign in as the owner.
My storefront shows "temporarily unavailable".
The plan was unpaid for 30 days after the term ended. Choose a plan on Settings → Plan and pay, or ask your partner to renew. The storefront returns as soon as the plan is paid.
My store is closed. Is my data gone?
No. Your data is kept. Download a backup from the notice on Settings → Plan, or choose a plan to reopen the store.
Where is my free month?
Pay for your first month. Your first paid period is then extended by one month at no charge.
I want a different partner to pay from now on.
Take the plan over yourself first. Then arrange the new set-up with that partner.
Connect your in-store POS system
For store owners who already sell in-store with their own POS software: connect it to your store so it can read your products and stock and send every sale it rings up into your Orders, with stock kept in step at the right location.
Illustrated guide: lulu.us.com/help/guide-connect-local-pos
Before you startThis guide is for store owners (or staff with the "Manage and install apps" permission). You need your POS software's settings screen open, and ideally your POS provider or developer at hand — your POS must support a Lulu or Shopify-style connection (most Shopify connectors work with a different shop address and token). If you use the Lulu register (Point of Sale in your admin) you don't need this guide — it is already connected.
1. Open Settings → Apps and sales channels → Develop apps
Sign in to your store admin, open Settings, then Apps and sales channels, then Develop apps. Near the top you'll see a card called "Connect a POS system".
- If you don't see the button, ask the store owner for the "Manage and install apps" permission.
2. Click "Connect a POS system"
Give the connection a name you'll recognise (for example "Counter tills") and choose the store location the POS sells from. Sales the POS sends without naming a location are recorded at that location, and stock is taken from there.
- The access list is already filled in with exactly what a POS needs: read products, read and update stock, read locations, read and add customers, read orders, and send POS sales.
- You can untick extras such as adding customers — but "Send POS sales" must stay on.
3. Copy the access token
Click "Connect and get token". The access token is shown once — copy it straight away and keep it somewhere safe. If you lose it, click "Install (new token)" on the app card to make a new one and revoke the old one.
- Never share the token by email or chat — anyone who has it can send sales into your store.
4. Paste the token into your POS
In your POS software's connection settings, enter your store's address (your own domain or your store's web address) as the shop URL and paste the token. The POS then downloads your products and stock levels and starts sending each sale it completes. Your POS developer will find the full technical details in the developer guide linked on the card.
- Each sale carries the POS receipt number, so a sale that is sent twice (for example after the Wi-Fi drops) is only recorded once.
- Sales made while the POS was offline keep the time they actually happened.
5. Check that sales are coming in
Ring up a small test sale on the POS. Back on the Develop apps page, click "Recent POS syncs" on your POS app card — the sale appears there with its receipt number, location and total. It also shows under Orders: use the Channel filter and choose "External POS".
- Counter sales arrive as Paid and Fulfilled, and the stock at that location goes down.
- In Analytics, External POS sales have their own row under Sales by channel, and Point of Sale → Reports shows them in their own block — they are never mixed into Lulu register figures.
6. Change the location or disconnect later
On the app card you can switch which location sales land at. To disconnect the POS completely, click "Uninstall" — every token for it stops working immediately. Orders it already sent stay in your store.
Completion checklist
- The POS app shows on Develop apps with an Active token.
- A test sale appears under Recent POS syncs and under Orders → Channel: External POS.
- Stock for the test item went down at the right location.
- The token is stored only in the POS settings.
Troubleshooting
My POS says the token is invalid.
Check that the shop address in the POS is this store's address — a token only works on the store it was made for — and that the token wasn't revoked or the app uninstalled. Make a new token with "Install (new token)" if in doubt.
A sale was refused because an item is out of stock.
Items set to stop selling when out of stock can't go below zero at that location. Correct the stock count in Products → Inventory (or from the POS), or let your POS developer send such sales with the option that records them even when the count disagrees.
Sales show up at the wrong location.
Change the location on the POS app card, or ask your POS developer to send the location with each sale.
A sale appears twice.
Each sale must carry its own receipt number. If your POS reuses or omits receipt numbers, ask your POS provider to send a unique receipt number (or an Idempotency-Key) with every sale.
Online orders don't reduce stock in my POS.
Your POS needs to listen for stock updates (the inventory_levels/update webhook) or check for changes regularly. The developer guide explains both.
Connect an AI agent to your store
Let the AI assistant you already use — ChatGPT, Claude (claude.ai, Claude Desktop or Claude Code), Cursor or an automation tool — work inside your store: update products and photos, stock, orders, discounts, pages and your theme, or handle routine jobs on a schedule. You choose exactly what it may touch, it can only ever reach your own store, every action is logged, and you can switch it off at any time.
Illustrated guide: lulu.us.com/help/guide-connect-ai-agent
Before you startThis guide is for store owners (or staff with the "Manage and install apps" permission). Have your AI app open — ChatGPT, Claude (claude.ai or Claude Desktop), Claude Code, Cursor or another MCP app. The AI can only ever reach your own store, nothing changes until it actually makes a change, and everything it does appears in your store's audit log.
1. Find your store's MCP address
Sign in to your store admin and open Settings → Apps and sales channels → Develop apps. The "Connect an AI agent" card shows your store's MCP address with a Copy button, and step-by-step instructions for each AI app. The address looks like https://your-store.lulu.us.com/admin/mcp.
- Use your store's own address — never the admin address (admin.…).
- Opening the address in a browser only shows a short help page. It is meant to be pasted into an AI app.
- Editing your theme? The same instructions are under Online Store → Themes → Customize → Edit with AI.
2. ChatGPT: add the store as a connector
In ChatGPT open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. Back in Apps & Connectors, click Create. Give the connector a name, paste your store's MCP address as the MCP server URL, choose OAuth for authentication and click Create. ChatGPT sends you to your store admin to approve (see "Approve the connection" below).
- Developer mode needs a ChatGPT plan that offers it.
- No token to copy — the sign-in takes care of it.
- Afterwards, start a new chat, switch the connector on from the + menu and ask "What store are you connected to?"
3. Claude (claude.ai or Claude Desktop): add a custom connector
In Claude open Settings → Connectors and click Add custom connector. Give it a name, paste your store's MCP address and click Add. Then click Connect on the new connector — Claude sends you to your store admin to approve (see the next step).
- A connector added on claude.ai also works in Claude Desktop and the Claude mobile app on the same account.
- In a chat, turn the connector on from the tools menu and ask "List my store's themes."
4. Approve the connection
ChatGPT or Claude opens a page in your store admin that asks whether to allow the app. Check where you'll be sent back to (chatgpt.com or claude.ai), choose what it may do — Full access, Read only or Theme editing only — and how long the connection lasts (30, 90 or 365 days), then click Allow. You are taken back to the app, connected.
- Only access you hold yourself is granted. Theme code (custom scripts) is never part of these choices.
- An app the page can't verify shows a warning — only approve it if you started the connection yourself just now. Never approve a request someone else sent you.
- The connection shows up on Develop apps as an "AI agent · MCP" app.
5. Claude Code: create a token and run one command
Claude Code and other MCP apps that take a token connect with one (Cursor can sign in instead — next step). On the Connect an AI agent card, open the Claude Code tab and click Create a token. Name the connection, pick how long the token lives (30, 90 or 365 days) and the access, then click Connect and get token. Copy the Claude Code command shown and run it in your terminal.
- The token is shown only once. Lost it? Revoke it and create a new one.
- Then START A NEW Claude Code session (or type /mcp). A session that was already open can't see the store — even though "claude mcp list" says Connected.
- The command includes --scope user so the store works in every folder, not just the one you ran it in.
- Ask "List my store's tools" to check.
6. Cursor and other MCP apps
Cursor needs no token. In Cursor open Cursor Settings → Tools & MCP (older versions: MCP) and click New MCP Server — Cursor opens its mcp.json file. Copy the block from the Cursor & others tab (it holds only your store's MCP address, no headers line): if the file is empty paste the whole block, otherwise add just your store's entry inside mcpServers, and save. Your store shows Needs login — click Login (or Connect): this admin opens — sign in, choose the access and click Allow. When the dot turns green, open a new chat and ask "What store are you connected to?" If Cursor shows 401 Unauthorized, your mcp.json still has a headers / Authorization line (often the example <token>, which is not a real token): delete that line and save, and Cursor offers the sign-in. Other MCP apps that cannot sign in use a token: create one as in the previous step, press Copy on the "Cursor & other apps" block shown with it (don't retype the token — copy the whole block so it arrives complete), paste it into the app's MCP servers configuration and restart the app.
7. Use it
Ask in plain language. Start with something harmless — "what store are you connected to?" or "list my five newest products" — then give it a job: "add this photo to the Aurora necklace", "set the stock of SKU HJ-1002 to 12", "mark order #1042 as fulfilled with this tracking number", or for the theme: "on theme #661, change the accent colour to #355e45 and show me before publishing".
- It only sees the tools for the access you chose, so it can't even try anything else.
- Deleting, cancelling, refunding, publishing a theme and similar actions always need it to confirm first.
- Theme changes appear when you reload the theme editor, and in Version history as an "agent save".
8. Watch and switch off
Every connection is listed on Develop apps with when it was last used. Every action — reads included — is in the store's audit log. Click Revoke on a token, or Uninstall on the app, to cut the AI off immediately.
- Connections also stop when the store is suspended or handed over, or when the person who approved them is removed or suspended.
Completion checklist
- The connection appears on Develop apps as an "AI agent · MCP" app.
- Your AI app lists the store's tools (for example get_store_info, list_products, list_themes).
- Asking which store it is connected to names your store.
- A test change you asked for shows up in the admin and in the audit log.
Troubleshooting
Claude Code says Connected, but the chat says it can't reach my store.
Claude Code only loads servers when a session starts. Close that chat and start a new Claude Code session (or type /mcp), then ask it to list your store's tools.
ChatGPT opened the admin in a browser and asked me to sign in.
ChatGPT wasn't using the connector for that request — it tried to browse to the admin link instead. Use a normal chat (not Agent mode), pick your store's connector from the + menu, and describe the change in words, for example “On the Svena copy theme, add a hover animation to the hero.” You don't need to paste admin links; the connector already knows which store it is.
I opened the address in my browser and saw a message instead of my store.
That's expected — the address is for AI apps. Paste it into ChatGPT or Claude as a connector, or use the Claude Code command.
ChatGPT or Claude can't find Create / Add custom connector.
In ChatGPT, turn on Developer mode first (Settings → Apps & Connectors → Advanced settings); it needs a plan that offers it. In Claude, custom connectors are under Settings → Connectors.
The approval page says the request expired.
The sign-in must be approved within 15 minutes. Go back to the AI app and connect again.
My app says the connection is unauthorized.
The token was revoked or expired, was pasted incompletely, or the address isn't your store's own /admin/mcp address. Revoke it and create a fresh connection.
The AI says a tool needs access it doesn't have.
A connection only has the access chosen when it was created, and never more than the person who approved it holds. Connect again and choose more access.
Show a pop-up only to the right visitors (PopForm targeting)
For store owners: use the Targeting settings of the Offer pop-up to show it only on the right devices and pages, to new or returning visitors, from the right traffic source or country, and within a cart value range — and choose when it opens.
Illustrated guide: lulu.us.com/help/guide-popform-advanced-targeting
Before you startYou need the PopForm Offers Pop-up app installed on your store and an Offer pop-up section added in the theme editor (Online Store → Themes → Customize). Advanced targeting is included on every PopForm plan. Every targeting rule starts switched off, so a new pop-up shows to everyone until you change a setting.
1. Open the pop-up's settings
In your admin go to Online Store → Themes and open the theme editor with Customize. Add an "Offer pop-up" section from the Marketing group with + Add section (or select the one you already have). Its settings appear in the panel on the right. Scroll to the "Targeting" group.
- Everything in Targeting is checked in the shopper's browser right before the pop-up would open.
- Save your theme changes (and publish if you are editing a draft) before you test on your live store.
2. Choose when it opens
Under "Show trigger" pick one of: "After a delay" (set "Show after (seconds)", 0 to 60), "Exit intent (desktop)", "Scroll depth" (set "Scroll depth" as a percentage from 1 to 100), or "Time on page" (set "Time on page (seconds)", 1 to 600). Only the trigger you pick is used.
- Exit intent works on desktop only. It opens the pop-up when the visitor's mouse leaves through the top of the browser window. A phone has no mouse, so on a phone this trigger never fires — pick Scroll depth or Time on page if many of your shoppers are on mobile.
- "Show again after (days)" (1 to 90, default 7) controls how long a shopper who closes the pop-up or signs up is left alone.
- Under the Schedule group, "Offer starts" and "Offer ends" keep the pop-up from opening outside those dates. Leave them blank to run all the time.
3. Pick the device
Under Targeting, set "Device" to "All devices", "Mobile only" or "Desktop only". Use this when an offer only makes sense on one kind of screen.
4. Limit it to certain pages
Use "Only show on URLs containing" to list the pages that may show the pop-up, and "Never show on URLs containing" to list pages that must not. Type one rule per line, up to 10 lines each.
- Rules are plain text, not patterns: a rule such as /collections/sale matches any page whose address contains it. Capital letters do not matter.
- Leave the include box blank to allow every page.
- A page that matches an exclude rule never shows the pop-up, even if it also matches an include rule.
5. Choose new or returning visitors
Set "Visitor" to "Everyone", "New visitors" or "Returning visitors". Lulu remembers visitors with a small cookie set on their first visit — they do not need an account.
- A visitor counts as returning once their first visit is more than 30 minutes old. Until then — for example while they open a few products in the same visit — they are still new.
- If a shopper clears their cookies they count as new again.
6. Target by where visitors come from
"Traffic source" can be "Any source", "Direct", "Search engines", "Social", "Email" or "Other referrals" (the same grouping your store analytics use). For campaign links, fill in "UTM source equals" (for example klaviyo) and/or "UTM medium equals" (for example email).
- UTM values are not case-sensitive. A blank field is ignored.
- When you set both a traffic source and a UTM value, the visitor has to match both.
7. Target by country
In "Countries" type two-letter country codes separated by commas, for example US, CA, GB. Leave it blank for every country.
- If Lulu cannot tell which country a visitor is in, the pop-up is not shown while a country list is set.
8. Set a cart value range
"Minimum cart value (cents)" and "Maximum cart value (cents)" show the pop-up only when the shopper's cart total falls inside the range. Enter whole numbers in cents in your store's currency: 5000 means 50.00. Leave 0 for no limit. The limits include the minimum and the maximum themselves.
- For shoppers browsing in another currency, the limits are converted automatically.
- If you swap the two numbers by mistake, Lulu reads the smaller one as the minimum so the pop-up does not disappear.
- If the cart cannot be read, the pop-up is not shown while a cart limit is set.
9. Test it
Open your store in a private browser window and visit as the audience you picked (for example on a phone, from a campaign link, or with an empty cart). If a pop-up does not appear, check the other rules one at a time — it must pass every rule you set.
- Because of "Show again after (days)", a window you have already closed the pop-up in will not show it again until that time passes. Use a fresh private window for each test.
Completion checklist
- The trigger, schedule and "Show again after (days)" are what you want.
- Each targeting rule you set is on purpose; the rest are left at All / Any / blank / 0.
- You tested as the intended audience in a fresh private window.
- You know your plan's monthly pop-up view allowance and it is enough for your traffic.
Troubleshooting
Is targeting included on my plan?
Yes. Advanced targeting is listed on every PopForm plan, including the free development-store plan.
Do visitors who do not match my rules count toward my monthly pop-up views?
No. The rules are checked before the pop-up opens, so a visitor who fails a rule does not see it and is not counted toward your plan's monthly pop-up views.
The pop-up never shows on phones.
Check whether the trigger is "Exit intent (desktop)" — it does not fire on phones. Choose a delay, scroll depth or time on page instead. Also check that Device is not set to "Desktop only".
The pop-up does not show for anyone.
A country list or cart value limit blocks visitors when the country or cart cannot be determined. Clear those fields to check. Also confirm the Offer starts and Offer ends dates and that the page address is not matched by a "Never show" rule.
Returning visitors do not see it on their second page.
A visitor only counts as returning after 30 minutes from their first visit. Test again later with the same browser.
My cart limits behave oddly in another currency.
Enter the limits in your store's main currency, in cents. For shoppers using another currency they are converted automatically, so the limit is not exactly the number you typed in their currency.
Can I use patterns or regular expressions in the URL rules?
No. Rules are plain text that the page address must contain. Use short, distinctive parts of the address such as /collections/sale.
Customize the Quick view button and pop-up (QuickPeek)
For store owners: turn on Quick view on your product cards and restyle the button and the pop-up — text, style, position, colours, width, photo position, corners, animation and which details show — from the theme editor.
Illustrated guide: lulu.us.com/help/guide-quickpeek-customize-quick-view
Before you startYou need the QuickPeek Quick View app installed. Styling the button and pop-up takes effect on the Growth plan or higher; on the Free plan it takes effect only while your store is still a development store. On any other plan the store keeps the default Quick view look — you can still open and preview the settings. Every setting starts at its default, which keeps today's look, so nothing changes until you change it.
1. Turn Quick view on
In your admin go to Online Store → Themes and open the theme editor with Customize. Open the Collection page and select the "Collection banner & grid" settings. In the Product cards group, tick "Show a “Quick view” button". Pointing at a product card now reveals a Quick view button that opens the product in a pop-up; the card itself still goes to the full product page.
- The extra settings below only appear in the Quick view group; the layout picker only appears once Quick view is on.
2. Rename and restyle the button
In the "Quick view" group set the button. "Button text" is blank by default, which shows "Quick view" (translated for your shoppers); you can type your own, up to 24 characters. "Button style" is "Solid (default)", "Outline" or "Icon only". "Button position on the card" is "Centre of the photo (default)", "Bottom centre", "Bottom left", "Bottom right", "Top left" or "Top right".
- "Button colour" overrides the theme's button colour; leave it blank to keep the theme's. The text colour adjusts automatically so it stays readable.
3. Style the pop-up
Set the pop-up's look: "Pop-up accent colour" (sale price, selected size, vendor line and links; blank uses the theme accent), "Pop-up width" (Small, Medium (default), Large), "Photo position" (Photo on the left (default), Photo on the right, Photo on top), "Corner radius" (Theme default, Square, Small, Medium, Large), "Background darkness" (Light, Medium (default), Dark, Darkest) and "Open animation" (Fade and rise (default), Fade, Slide up, None).
4. Choose which details show
Tick or untick: "Show vendor" and "Show quantity selector" and "Show “View full details” link" (all on by default), and "Show star rating", "Show a short description" and "Show SKU" (off by default).
- Products with no reviews show no star rating even when "Show star rating" is on.
5. Pick a layout (QuickPeek Pro)
"Quick view layout" offers Centered modal (default), Side drawer, Bottom sheet, Split media / details, Gallery-first and Minimal. This is a separate QuickPeek Pro feature: on other plans the pop-up always uses the centered modal, whatever is picked.
- The Quick view styling settings above work on Growth and Pro. The layout picker needs the Pro plan.
6. Save and check your store
Save the theme (and publish if you are editing a draft), then open your live store and point at a product card. If the look did not change, see the plan notes below.
- You can undo a change by setting the field back to its default, or leaving it blank.
Completion checklist
- Show a “Quick view” button is ticked.
- The QuickPeek app is installed and your plan is Growth or higher (or a development store on Free).
- The button and pop-up look right on both a phone and a desktop screen.
- Layout choices other than the centered modal are only expected if you are on QuickPeek Pro.
Troubleshooting
I changed the settings but my live store looks the same.
Styling takes effect on the Growth plan or higher, or on the Free plan only while the store is a development store. On other plans, or if the QuickPeek app is not installed, the store keeps the default look. Upgrade the app plan in the App Store.
Do I lose my settings if I am on a lower plan?
The values stay saved in the theme editor; they are simply not applied to your storefront until your plan allows them.
Where is the Quick view group?
In the theme editor, on the Collection page template, in the "Collection banner & grid" settings. If you do not see it, check that the QuickPeek Quick View app is installed.
The layout setting does nothing.
Layouts other than the Centered modal need the QuickPeek Pro plan; other plans always use the centered modal.
Can I use any colour?
Use a normal hex colour such as #1a2b3c. Anything else is ignored and the theme colour is used.
My button text is cut off.
The text is limited to 24 characters. Shorten it or choose "Icon only".
Drop Shipping plan limits for synced products
For store owners on the Drop Shipping app: what counts toward your plan's synced product limit, what happens when you reach it, how to free a slot, and how to check your usage and upgrade.
Illustrated guide: lulu.us.com/help/guide-dropshipping-product-limits
Before you startThis guide is for stores that have the Drop Shipping app installed. Each store has its own Drop Shipping plan and its own limit. Without the app installed, no synced product limit applies.
1. Know what counts
Your plan limits the number of "active synced products": products in your store that are linked to a supplier and are not archived. Draft products count too — a supplier product you import arrives as a draft and is already being kept in sync, so it uses a slot from the moment it is imported.
- Products you duplicate, create yourself, or restore from a backup are not linked to a supplier, so they do not count.
- Archived products do not count.
2. Check the limit for your plan
The limit per Drop Shipping plan is: Launch 250 products, Growth 2,500, Scale 10,000 and Enterprise 50,000.
- Launch is 19 a month, Growth 49, Scale 99 and Enterprise 299 (US dollars). Check the plan page in the App Store for the current price.
- Separately, the plan also limits how many stores of a store group can be read in the multi-store reports (1, 1, 3 and 10).
3. See your usage
In your admin open Dropshipping. A usage card near the top shows a line such as "183 of 250 synced products", the name of your plan, and a bar. From 80 percent a warning appears, and at or over the limit a stronger notice appears with a "See plans" link to the Drop Shipping app page.
- The same figure appears in the Usage card of the Drop Shipping app in the App Store.
4. What happens when you reach the limit
Two things are refused: importing a supplier product, and taking an archived supplier product out of the archive. A bulk import adds products up to your limit, stops there, and its result message reports how many were left out (for example "3 products were not added: the synced product limit (250) is reached"). You can retry them after you free slots or upgrade.
- Nothing you already have is removed, archived or stopped. All existing products keep syncing stock, cost and tracking.
- If a downgrade leaves you over your limit, the same applies: everything keeps syncing and only new additions are refused until you are back under the limit.
5. Free a slot
Go to Products and archive (or delete) products you no longer sell from your supplier. Archived and deleted products stop counting, so the usage card goes down and you can import again.
- Archiving is best if you may sell the product again, but note that un-archiving it uses a slot again and is refused at the limit.
6. Upgrade for a higher limit
On the usage card click "See plans", or open the Drop Shipping app in the App Store, choose a larger plan and confirm. The new limit applies as soon as the plan changes. The message you get when a limit is reached also names the plan that raises it.
Completion checklist
- You know your plan's limit and your current usage.
- Products you no longer sell are archived or deleted.
- Any bulk import that was cut short has been repeated after freeing slots or upgrading.
Troubleshooting
Do draft products count?
Yes. Any product linked to a supplier that is not archived counts, drafts included.
I archived a product but my usage did not change.
Reload the Dropshipping page. If the product is still listed as active elsewhere (for example a second copy linked to a supplier), it still counts.
My bulk import stopped part-way.
It stops at your limit and reports how many products were not added. Free slots or upgrade, then import the rest.
Will products be removed if I downgrade?
No. Nothing is removed or stops syncing. You will only be refused new imports and un-archiving until you are back under the limit.
I can't un-archive a product.
Un-archiving counts the product again, so it is refused at the limit. Archive something else or upgrade.
I do not see the usage card.
The card appears for stores with the Drop Shipping app installed and a plan limit. Check the app is installed in the App Store.
Charge subscriptions to a saved card automatically (Recur Subscriptions)
For store owners: let subscribers pay each Recur subscription delivery automatically with a saved card, what your store needs first, what shoppers agree to, what happens each cycle and when a charge fails.
Illustrated guide: lulu.us.com/help/guide-recur-automatic-card-payments
Before you startYou need the Recur Subscriptions app installed and at least one subscription plan. Automatic charging is optional and off by default; until you switch it on, every subscription order is a normal cash-on-delivery order. It is available only if your store takes cards through its own Stripe account, with saved cards switched on.
1. Check what your store needs
Automatic charging can be switched on only when all of these are true: your store takes cards with Stripe on your own Stripe account (your own secret key, set up in Settings → Payments), saved cards for Stripe are switched on in Settings → Payments, your own Stripe webhook signing secret is added in Settings → Payments → Stripe (the endpoint is your store address followed by /api/store/payments/webhook, with the payment_intent events), and your store currency is one Stripe charges in two decimals.
- Stripe currencies with no decimals or three decimals (for example JPY, KRW, KWD) are not supported.
- Stores that only pay through Lulu's own payment connection, or through a redirect gateway, keep cash on delivery exactly as before.
2. Switch it on
In your admin go to Products → Subscriptions. In the "Payments" card tick "Charge the saved card automatically" and click "Save". If the box cannot be ticked, a yellow note under it tells you which requirement is missing.
- Untick it and save to stop all automatic charges. Orders then go back to cash on delivery.
3. What shoppers see and agree to
On a product with a subscription, a signed-in shopper with a verified email and a saved card sees "Pay each delivery automatically with my saved card". It is never pre-ticked. They choose a card and tick the box that authorises automatic payments, which states that each delivery is charged its full order total — the item price plus shipping and any tax — on the day each order is placed, until they switch to pay on delivery, remove the card, or pause or cancel. Their bank may ask them to confirm the card. Shoppers without a verified email or a saved card keep paying on delivery.
- Shoppers can also set this up later from My account → Subscriptions with "Pay automatically with a card".
4. What happens each cycle
When a delivery is due, Lulu places the order as usual and then charges the shopper's saved card the full order total. If the charge works, the order is marked paid like any card order and the usual confirmation and order automation run. You see "Card" on the subscription in Products → Subscriptions and the result under "Last card charge" on the subscription's page.
- Refunds work like any other card order: refund the order from the order page.
5. What happens if a charge fails
The order stays open to pay on delivery, nothing is lost, and the shopper gets one email with a link to their account to pay now, change the card, or pay on delivery. Lulu tries the card once more after 3 days, unless the order is paid or delivered before then. If that retry also fails, the subscription is flagged for you with "Card payment failed" in the list and a warning on the subscription's page.
- You can edit the wording of the email under Subscription emails on the Subscriptions page.
- Orders you can see as unpaid after a failed charge are collected on delivery.
6. How a shopper changes card or goes back to pay on delivery
In My account → Subscriptions a shopper uses "Change card" to pick another saved card, or "Switch to pay on delivery" to stop automatic charges for that subscription. When a charge has failed, the same page offers to pay now.
- If a shopper removes their saved card, their subscription goes back to cash on delivery.
Completion checklist
- Your store uses its own Stripe account with saved cards and its own Stripe webhook set up.
- "Charge the saved card automatically" is ticked and saved.
- You made a test subscription as a shopper and saw the consent wording.
- You know how to find a flagged subscription in Products → Subscriptions.
Troubleshooting
The box is greyed out.
One of the requirements is missing. Read the yellow note under the checkbox: it names what to fix (turn on Stripe, use your own Stripe key, add your webhook signing secret, turn on saved cards, or a store currency that Stripe charges in two decimals).
Which plan includes this?
It is part of Recur Subscriptions on every plan. You also need a store that takes cards through its own Stripe account.
A subscriber is charged more than the product price.
Each order is charged its full total: item price plus shipping and any tax. The shopper's agreement says so.
A card payment failed. What do I do?
The order is still open for pay on delivery and the shopper was emailed. After one more try three days later, the subscription is flagged for you. You can also contact the shopper or collect on delivery.
Will shoppers who did not opt in be charged?
No. Only shoppers who ticked the explicit consent and chose a saved card are charged automatically. Everyone else pays on delivery.
How do I stop charging a subscriber?
The shopper can choose "Switch to pay on delivery", or you can cancel the subscription from its page. Turning the setting off stops automatic charges for every subscription.
How do I refund an automatic payment?
Refund the order like any card order from its order page.
Set up pre-orders with Presale Pre-orders
For store owners: install the Presale Pre-orders app, build a pre-order campaign (products, when the Pre-order button shows, ship date, full payment or a deposit), publish it, see what shoppers see, collect the remaining balance and place a test order to check it all works.
Illustrated guide: lulu.us.com/help/guide-presale-preorders
Before you startYou need access to Orders and Products in your store admin, and at least one active product to put on pre-order. Pre-orders are not built in: they come from the Presale Pre-orders app in the App Store (handle `presale-preorders`). Until the app is installed and a campaign is published, nothing changes on your storefront. Taking a deposit (split payment) and giving a pre-order discount need the app's Growth plan or higher; the Launch plan sells pre-orders at the full price.
1. Install Presale Pre-orders
Open the App Store in your admin and find Presale Pre-orders, or go straight to `/admin/app-store/presale-preorders`. Click “Install”. A window shows what the app can access and what it costs; click “Install” again to confirm. Installing a paid app starts its free trial, and a message tells you when the trial ends. Once it is installed, “Pre-orders” appears under Orders in the left menu (`/admin/presale`).
- Before the app is installed, the Pre-orders page only shows “View in the App Store”.
- Plans: Launch sells pre-orders at the full price. Growth adds split payments (a deposit now, the rest later, or nothing now) and pre-order discounts. Scale adds “Advanced reporting”. Each plan has its own “Pre-orders a month” limit.
- Use “Start free trial” or “Choose plan” on the app's page to move to another plan.
2. Get your products ready
A campaign can only cover active products. If you want Pre-order to show only once a product sells out, that product's inventory must be tracked and must not keep selling at zero: on the product page, in the “Inventory” card, turn on “Inventory tracked” and leave “Continue selling when out of stock” unticked. The Pre-order button then takes over when the quantity reaches 0.
- If a product keeps selling when out of stock, or its quantity is not tracked, it never counts as sold out. Choose “Always, whatever the stock level” for it instead (see step 5).
- On the product page, “Manage pre-orders in Presale” takes you to the Pre-orders page.
3. Create a campaign
Go to Orders → Pre-orders and click “Create campaign”. Under “Basics”, type a “Campaign name”, for example Spring drop. The name labels the campaign in reports and on each order, and on the product page it is also the name of the pre-order option shoppers pick, so give it a name shoppers can read. Fill in the panels below (steps 4 to 8), then click “Create campaign”. The campaign is saved as a Draft and its page opens. Nothing changes on your storefront until you publish it.
- “Coming soon” shows a badge and a notify-me form instead of a buy button. It lasts until the campaign’s Starts date, when pre-orders open by themselves (checked every 15 minutes). With no start date, nothing can be bought until you turn it off. Use it to build interest before a launch.
4. Choose the products
In the “Products” panel, click “Choose products”, search for products in the “Add products to this campaign” window and add them. They appear as chips, and you can remove one with ×. To put the whole catalogue on pre-order (a store-wide back-order), tick “Every product” instead.
- Every variant of a chosen product is covered. You can't pick single variants here.
- A unit cap applies to the whole campaign, not to each variant.
5. Set the rules: when Pre-order shows, dates and limits
In the “Rules” panel, under “When Pre-order shows”, choose one option. “Only when out of stock”: Pre-order replaces Sold out when stock reaches 0, and Add to cart comes back when you restock. “Always, whatever the stock level”: Pre-order replaces both Add to cart and Sold out. “Only while stock lasts”: each pre-order uses up a unit of your stock when it is sold, so the offer closes when the stock runs out. Then set “Starts” and “Ends” if you want a fixed window. If you leave Starts blank, the campaign opens when you publish. If you leave Ends blank, it stays open until you end it.
- “Total units” caps how many units the whole campaign can sell. Leave it blank for no limit. Checkout refuses the unit that would go over the cap.
- “Per customer” caps how many units one shopper can pre-order, counted across all of that shopper's orders in this campaign.
- For “Only when out of stock” and “Always, whatever the stock level”, the stock you hold isn't reserved when a pre-order is placed.
6. Set the expected ship date
In the “Shipping” panel, choose “Exact date” and pick a “Shipping date”, or choose “To be finalised” if you don't have a date yet. Shoppers then see “Ship date to be confirmed”. You can also add a “Ship note”, for example Ships in 2–3 weeks. It is shown with the date, or on its own when the date is to be finalised. The estimate appears under the buy button, in the cart and on the order.
- “Hold these orders from fulfillment” (on by default) keeps pre-orders out of your Unfulfilled queue until they are ready. Held orders are listed in Orders under the “On hold” tab.
- “Release the hold on the ship date” (on by default) releases the hold automatically on the shipping date. If you turn it off, or the date is “To be finalised”, you release each order yourself.
- If you later move a live campaign's ship date to a later day, Lulu updates the orders already taken and emails the affected shoppers the new date.
7. Choose how much shoppers pay at checkout
In the “Billing” panel, choose “Full amount” to charge everything at checkout, or “Split payment” to charge part now and the rest later. With “Split payment”, type the “First charge” as a percentage (“% of the price”). Enter 0 to take nothing now. A deposit is always a percentage; there is no fixed-amount deposit. Then choose “When to charge the rest”. “When you fulfil the order”: the balance falls due when the fulfillment hold releases. “On a specific date”: pick a “Balance date”. “A set time after checkout”: enter the number of “Days after checkout”.
- “Split payment” and “Pre-order discount” need the Growth plan or higher. On a lower plan, the Billing panel shows “Split payment” switched off with a “Growth plan” label and an upgrade line before you save, and a banner names the locked feature.
- “Pre-order discount” takes a percentage off the price (0 to 90) as a reward for ordering early. 0 means the normal price.
- Lulu never charges a saved card for the balance. When the balance falls due, the shopper gets an email with a link to pay it through your normal checkout, and you can send that request yourself at any time (step 12).
- Shipping, tax and tips are always charged in full at checkout. Only the product price is split.
8. Customise the wording and mixed carts
In the “Customisation” panel you can type your own “Button text” and “Badge text” (left blank, they use the defaults from Pre-orders → Settings, and then the standard “Pre-order”). Under “Mixed carts”, choose “Allow” to let shoppers buy in-stock items and pre-orders together (the whole order waits for the pre-order), or “Pre-orders only” so that a cart with a pre-order holds nothing else. “Countdown” adds a clock to the Pre-order launch banner section. The “Preview” box beside the fields shows the badge, the button and the payment and shipping lines.
- Your Button text replaces “Pre-order” on the product page buy button and the sticky bar; your Badge text replaces the “Pre-order” chip on product cards and the pre-order option on the product page, and also shows on the Coming soon chip and launch banner. Long text is shortened with “…”. Shoppers browsing in another language keep the translated “Pre-order”.
- Set defaults for new campaigns under Pre-orders → “Settings” → “Default storefront copy”.
9. Publish the campaign
On the campaign's page, click “Publish”. If the start date is in the future, the campaign becomes Scheduled and goes live on its own on that date. Otherwise it is Live straight away. If something is missing, a red banner says “Fix the highlighted fields, then publish.” and each field shows what to fix.
- Once the campaign is live, edits apply only to new pre-orders. Orders already placed keep the terms they were sold on.
- “End campaign” stops new pre-orders and leaves the orders already placed as they are. An ended campaign shows “Reopen”.
- “Delete” removes the campaign. Pre-orders it already took, and their holds and balances, stay in Commitments.
- The page header shows the status (Draft, Scheduled, Live or Ended), the “Campaign ID” and the units sold.
10. Set reminders and other defaults
Go to Pre-orders → “Settings” (`/admin/presale/settings`). Under “Balance reminders”, “Remind this many days before” takes a comma-separated list. The default `3, 0` sends one reminder three days before the balance is due and one on the day. “Chase an overdue balance after” (default 3 days) sends one overdue email. Each shopper gets each reminder once. Under “Delay notice”, the “Extra line” is added to the email shoppers get when you move a ship date later. Click “Save”.
- These reminders cover balances due on a date (“On a specific date” or “A set time after checkout”). A balance due when the order ships is requested in the “ready to ship” email sent when the hold releases.
- Lulu checks for due campaigns, holds and reminders every 15 minutes. “Run now” on the Pre-orders page runs that check straight away.
- Emails go out only if your store's email sending is set up.
11. Know what shoppers see
On a covered product, under “Purchase options”, shoppers see an option named after your campaign with a “Pre-order” tag. Under it is a payment line such as “Pay 30% now, rest when it ships” or “Pay in full now”, and a shipping line such as “Ships by 12 Nov 2026”. The buy button reads “Pre-order”. When few units are left on a capped campaign, it also says “Only 3 left for pre-order”. In collections and search, a sold-out product that can still be pre-ordered shows a “Pre-order” chip instead of Sold out.
- Cart and checkout: each pre-order line reads “Pre-order · Ships by … · … due later”. With a deposit, checkout shows “Due today” and “Due later”.
- Checkout asks the shopper to tick a box confirming what is charged today and when the rest is due. The order can't be placed until it is ticked.
- The pay button reads “Pay” plus today's amount, or “Place pre-order” when nothing is due today.
- A “Coming soon” campaign shows a “Coming soon” chip (or your Badge text), a “Launches …” date if you set a start date, and a notify-me form instead of the buy button.
- Optional: in the theme editor, add the “Pre-order launch banner” section and enter the Campaign ID to show the ship date, a countdown and a notify-me form.
12. Track pre-orders and collect the balance
The Pre-orders page shows “Units on pre-order”, “Pre-order orders”, “Collected”, “Balance outstanding” and “Overdue”, plus a “Fulfil next” list and your “Campaigns”. “All commitments” opens the Commitments page, with one row per pre-ordered line. You can filter by “On hold”, “Balance due” or “Overdue”, use “Release” to free a hold, use “Collect payment” to open the order, and download everything with “Export CSV”. An order that has paid its deposit has the payment status “Partially paid” and is listed under the “Unpaid” tab in Orders.
- On the order page, a card shows “Balance due”, “Payment received” and “Due”. “Collect payment” emails the shopper a link to pay the balance. It doesn't charge anything by itself.
- The shopper pays from their order status page with “Pay balance”. The button appears only if the order was paid through a redirect payment gateway that is still switched on in your store. Orders paid by card (Stripe), PayPal, bank transfer or cash on delivery can't pay the balance online. Collect that money yourself and record it with “Mark as paid”.
- “Edit due date” changes when the balance is due. Leave the date blank to make it due when the order ships.
- When the whole balance is in, the card shows “Paid in full”.
13. Place a test order
Publish a test campaign on one product, for example “Only when out of stock” on a product whose tracked quantity you set to 0, with an exact ship date. Open the product on your storefront in a private window. Check the “Pre-order” button and the shipping and payment lines, add it to the cart, tick the confirmation box at checkout and pay with a payment method in test or sandbox mode, or with a manual method such as cash on delivery. Then check the admin: the order is on hold under the “On hold” tab and appears on the Pre-orders page and in Commitments.
- To test a deposit, use a campaign with “Split payment” (Growth plan or higher) and pay with a redirect gateway in sandbox mode. Check that the order shows “Partially paid”, then click “Collect payment” and pay the balance from the link in the email.
- To test a full-payment pre-order on any plan, use “Full amount”.
- When you're done, cancel and refund the test order, end or delete the test campaign, and put the product's stock back.
Completion checklist
- Presale Pre-orders is installed and “Pre-orders” shows under Orders.
- You are on the Growth plan or higher if you want a deposit or a pre-order discount.
- Products set to “Only when out of stock” have “Inventory tracked” on and “Continue selling when out of stock” off.
- The campaign has products (or “Every product”), a ship date or a ship note, and a valid billing setup.
- The campaign shows Live (or Scheduled) after you click “Publish”.
- A covered product shows the “Pre-order” button with a shipping and payment line.
- Balance reminders and the delay notice are set under Pre-orders → “Settings”.
- A test order was placed, held, listed in Commitments and, for a deposit, collected with “Collect payment” or “Mark as paid”.
Troubleshooting
Publishing fails with “Fix the highlighted fields, then publish.”
Fix the message shown under each field: “Choose the products this campaign covers, or turn on “Every product”.”, “Set the expected ship date, or write a note explaining that it is still to be finalised.”, “Choose the date the rest is charged.”, “Enter how many days after checkout the rest is charged.”, “The end date must be after the start date.” or “The balance falls due after the ship date — collect it before you ship.” If it says “This campaign’s end date has already passed. Move it before publishing.”, change or clear “Ends”.
I can't select “Split payment” or set a pre-order discount.
Deposits, pay-later and pre-order discounts need the Growth plan or higher. On a lower plan the option is switched off with a “Growth plan” label from the start. Change your plan on the app's App Store page, then return to the campaign. On Launch you can still publish with “Full amount”.
The product page doesn't show the Pre-order button.
Check four things. The campaign must be Live: Draft, Scheduled and Ended campaigns offer nothing, and a “Coming soon” campaign shows Coming soon instead until its Starts date (or until you untick Coming soon and save). Today must fall between “Starts” and “Ends”. The product must be in the campaign and active. With “Only when out of stock”, the product must actually be sold out, meaning “Inventory tracked” is on, “Continue selling when out of stock” is off and the quantity is 0. A product that is in stock keeps its normal Add to cart. Also check that “Total units” hasn't been reached.
I changed the Button text but the product page still says “Pre-order”.
Check that the campaign is published and live (not Coming soon) and that the product is in it. Custom text only shows to shoppers browsing in the store's default language; other languages keep the translated “Pre-order”. Reload the page after saving.
A shopper sees “This item is back in stock — remove the pre-order line and add it normally”.
The campaign uses “Only when out of stock” and the product was restocked after the shopper added it. They need to remove the pre-order line and add the product again at the normal price.
A shopper sees “Pre-order items in this campaign are purchased on their own — remove the other items to continue”.
The campaign's “Mixed carts” is set to “Pre-orders only”. The shopper has to buy the pre-order in its own order, or you can switch the campaign to “Allow”.
Checkout says “Pre-order sold out”, “You can pre-order up to … of this item” or “Pre-orders are temporarily unavailable”.
The first means the campaign's “Total units” cap is reached. The second is the “Per customer” limit. The third means your plan's monthly pre-order allowance is used up; move to a bigger plan or wait for the next month.
Checkout says “Pay-later instalments aren’t available for pre-orders” or “Instalment plans aren’t available for pre-orders”.
Buy-now-pay-later rails and bank instalment plans can't be combined with a deposit or pay-later pre-order. The shopper needs to pick another payment method, or you can use “Full amount” billing for that campaign.
Checkout says “Please confirm the payment schedule to continue.”
Every cart with a pre-order asks the shopper to tick the box that states what is charged today and when the rest is due. The order can't be placed until they tick it.
“Collect payment” shows an error, or the button is greyed out.
The order needs a customer email; add one to the order first. If it says “Could not send the payment request — check Settings → Notifications”, your store's email sending isn't working. “There is nothing left to collect on this order” means the balance is already paid, and canceled orders can't be collected.
The shopper has no “Pay balance” button on their order page.
Shoppers can pay the balance online only for orders paid through a redirect payment gateway that is still switched on in your store. If the order was paid by card (Stripe), PayPal, bank transfer or cash on delivery, the page says “The store will contact you when the balance is due.” Collect the money yourself and click “Mark as paid” on the order.
Balance reminders were not sent.
Reminders go only for balances due on a date, at the days set in “Remind this many days before”, and each one is sent once. A balance due when the order ships is requested in the ready-to-ship email when the hold releases. The check runs every 15 minutes, and “Run now” on the Pre-orders page runs it straight away. Your store's email sending must be set up.
Pre-orders stay on hold after the ship date.
Holds release automatically only when the campaign has an exact “Shipping date” and “Release the hold on the ship date” is on. Otherwise click “Release” in Commitments, or “Release hold” on the order page.
Transaction fees
For store owners: what the platform transaction fee is, how it's worked out from last month's sales, where to see this month's running total and past statements, and what a fee freeze means.
Illustrated guide: lulu.us.com/help/guide-merchant-transaction-fees
Before you startThis guide is for store owners. You need a store owner or manager account with access to Settings → Billing. Your fee rate comes from your plan unless the platform has set your store its own rate; either way it's shown on this page, not something you configure yourself.
1. Find the Transaction fees card
Go to Settings → Billing. The "Transaction fees" card states your rate as a percentage of your sales, and how it's collected: if your store has a monthly bill, the card says "Your transaction fees are added to your monthly bill — there is nothing to pay separately." If not, it says "Each month's fees come as a statement you pay here." Refunds are always credited back at the same rate you were charged.
- If the platform has given your store its own rate instead of your plan's, the card notes "(your store's rate)".
- If your store pays no fee at all, the card explains why in place of a rate.
2. What counts toward the fee
Each month, the fee is your rate applied to that month's paid sales, after refunds. Orders you imported from another marketplace are never counted. Sales in a currency other than US dollars are converted to USD for the calculation, so the total can shift slightly if a conversion was still catching up when you checked.
- A refund credits back exactly the fee rate that applied when the sale was originally billed — so refunding an older order can credit a different rate than this month's.
- Amounts under $1.00 aren't collected on their own; they carry forward and are added to your next month instead.
3. Check "This month so far"
The card shows a live, read-only estimate for the current month: sales so far, the fee on those sales, any refund credit, and anything carried in from a previous month below the $1.00 minimum. This is an estimate only — the final amount is only set after the month closes.
- If it says fees haven't started yet, your first full month hasn't finished — fees only begin from your first complete month on the platform.
- "Some sales are still being converted to USD, so this may change" means the estimate may move a little before it's final.
4. Read your statements
Below the estimate, the Statements table lists one row per month: the month, your sales, the amount, a status, and any note about why. If your fees are added to your monthly bill, the status here mirrors what that bill shows. If your store pays fees on its own, a statement that's due shows a "Pay now" button, and you'll be taken to a secure payment page for that amount only.
- Every statement with at least one order behind it has a "CSV" button — it downloads every order counted that month, including which were billed, which were waived, and any refunds.
- "No statements yet" with a date under it tells you when your first one will be prepared.
5. If fees go overdue and your store is frozen
This only applies to stores that pay fees on their own (not on the monthly bill, which has its own pause rule — see "Your monthly bill"). If a standalone fee statement isn't paid in time, a banner at the top of the card shows the overdue amount. Left unpaid long enough, your store is paused until it's paid. Click "Pay now" on the overdue statement to clear it — paying in full brings your store back online right away.
- Reminders are sent as a statement approaches its due date and again after it's overdue, so you should never be surprised by a freeze.
- If fees are added to your monthly bill instead, there's no separate fee freeze — see the monthly bill guide for how pausing works there.
Completion checklist
- You can see your current fee rate and how it's collected.
- "This month so far" shows a sales and fee estimate once your first full month has started.
- You can open a past statement's CSV of counted orders.
- No overdue banner is shown on the Transaction fees card.
Troubleshooting
My estimate for this month looks too high or too low.
It's a live estimate, not the final number — it moves as new sales, refunds and currency conversions come in during the month, and only settles once the month closes.
A refund didn't credit what I expected.
The credit uses the rate that applied when that sale was originally billed, which can differ from your rate today if your plan or rate changed since.
An order I imported from another marketplace was still charged a fee.
Imported orders should never count. Contact support with the order number so it can be checked — this should not happen.
My store was paused for an overdue fee, but I don't see "Pay now" anywhere.
If your fees are on your monthly bill, pay the oldest unpaid bill instead — the fee itself has no separate payment button in that case. See "Your monthly bill".
The CSV button isn't showing on a statement.
It only appears once that month has at least one order counted. A month with nothing to bill (for example before your first full month) has no CSV.
Register as a partner
Apply for a Lulu partner account, understand the pending review, and sign in once the Lulu team approves you.
Illustrated guide: lulu.us.com/help/guide-partner-register
Before you startA partner account is how theme designers and app developers build for Lulu merchants. It is separate from a store login: use it at partners.lulu.us.com only. Applying is free. Use an email address you check, because every application is approved by hand and the decision arrives by email. You do not need a store of your own to apply.
1. Open the partner portal
Go to partners.lulu.us.com. The address opens the Partner Program card with two tabs: Sign in and Create account.
- You can also reach it from the Partner login link in the footer of lulu.us.com.
- The portal only works on partners.lulu.us.com. A store address or admin.lulu.us.com does not show it.
- If the card shows “The Partner Program is being provisioned. Check back shortly.”, the service is not ready yet. Try again later.
2. Switch to Create account
Select the Create account tab. The heading changes to Create your partner account and three fields appear.
- Your name or company: the name merchants see as the maker of your themes and apps.
- Email: the address you will sign in with and where decisions are sent.
- Password: at least 8 characters.
3. Know the field rules
The form checks each field before it sends anything. A field that is missing or wrong turns red and says what to fix.
- Name: at least 2 characters (up to 100). Message: “Enter your name or company name”.
- Email: must be a valid address. Messages: “Enter your email” or “Enter a valid email address”.
- Password: 8 to 72 characters. Message: “Password must be at least 8 characters”.
- If the email already has a partner account, the email field says “This email is already registered — sign in instead”.
4. Fill in your details
Type your name or company, your email and a password. Select the eye icon if you want to check the password you typed.
- Use a business email you control; it becomes your partner sign-in.
- One partner account covers both themes and apps. You do not choose a type.
5. Send the application
Select Apply for a partner account. By applying you agree to the Lulu Partner terms shown under the button.
- The button reads Sending application… while it works.
- You can send at most three applications a minute from one network. If you see a “too many requests” message, wait a minute.
6. Read the Application received message
A green banner confirms: Application received. We review every partner application by hand and will email you as soon as it is approved — usually within one to two business days.
- You are not signed in yet. There is no email verification link to click; the Lulu team's approval is the check.
- You also get an email with the subject “We received your partner application”.
- The Lulu team is told about your application automatically.
7. Signing in while you wait
If you try to sign in before a decision, the portal does not open. A blue notice says: Your partner application is still under review. We will email you as soon as it is approved.
- This notice only appears after a correct password, so it also confirms your password works.
- A rejected or suspended account sees a general “Incorrect email or password” message instead.
8. Watch for the decision email
When the Lulu team decides, you receive one email.
- Approved: subject “Your partner account is approved”, with a Sign in to the Partner Dashboard button.
- Not approved: subject “About your partner application”. It can include a note from the reviewer, for example what to add before applying again.
- No email after two business days? Check your spam folder, then contact Lulu support with the email you applied with.
9. Sign in after approval
Go back to partners.lulu.us.com, stay on the Sign in tab, enter your email and password, and select Sign in. You land on the partner Dashboard.
- Signing in again later works the same way. If you are already signed in, the portal opens the Dashboard straight away.
- Use Sign out in the top-right corner when you finish on a shared computer.
10. Know what approval unlocks
The top bar now links to Dashboard, Onboarding profile, Packages, Work, Leads, Listings and Reviews.
- Dashboard: create dev stores and client transfer stores, and send theme and app submissions for review.
- Listings: edit the themes and apps you have published. It is empty until your first submission is approved.
- Reviews: read and answer what merchants say about your listings.
- Onboarding profile, Packages, Work and Leads are for partners who also offer store-setup services to merchants.
- Approval opens your account. Every theme or app you submit is still reviewed separately before it appears in the Theme Store or App Store.
11. Reset a forgotten password
On the Sign in tab select Forgot password?, enter the email on your partner account and select Send reset link.
- The page always answers “If that email has a partner account, a reset link is on its way.” It never confirms whether an address is registered.
- The link works once and expires in 30 minutes. Choosing a new password signs you out everywhere else.
- Select Back to sign in to return to the sign-in form.
Completion checklist
- You applied at partners.lulu.us.com with an email you check.
- You saw the Application received banner.
- You received the approval email.
- You can sign in and see the partner Dashboard.
Troubleshooting
I applied but I cannot sign in.
Your application is still under review. The sign-in form shows a blue under-review notice after a correct password. Wait for the approval email; there is nothing else to confirm.
The email field says the address is already registered.
A partner account, or an earlier application, already uses that email. Use Sign in, or Forgot password? if you do not remember the password. The form gives the same answer for every existing application, whatever its status.
Sign in says “Incorrect email or password” but I am sure the password is right.
The same message is shown for a wrong password and for an application that was not approved or an account that was suspended. Use Forgot password? first; if that does not help, contact Lulu support with your partner email.
My application was not approved.
Read the note in the “About your partner application” email, fix what it asks for, and contact Lulu support. The team can approve the same application later; you do not need a new email address.
Do I need a verification link?
No. Partner applications have no email-verification step. The manual approval by the Lulu team replaces it.
Build apps and themes from start to finish
The complete partner path: create a dev store, build a theme in the real theme editor, export and submit it, propose an app listing, get through review, then maintain, update and support what you published.
Illustrated guide: lulu.us.com/help/guide-partner-build-apps-themes
Before you startYou need an approved partner account (see Register as a partner) and about half an hour. Everything here happens in two places: the partner portal at partners.lulu.us.com, and the ordinary store admin at admin.lulu.us.com, which the portal opens for you. You can build a theme end to end yourself. An app, on this platform, is a listing in the App Store: the portal publishes its description and pricing label, while the working integration, the store data it may use and any paid plans are set up together with the Lulu team.
1. Sign in to the partner portal
Go to partners.lulu.us.com, enter your email and password on the Sign in tab and select Sign in. You land on the Dashboard.
- The Dashboard lists, from top to bottom: Onboarding profile, Client stores, Stores and Your submissions.
- Themes and apps both start from this page.
2. Create a dev store
Under Stores select Create store. Choose Dev store, pick the Plan features it should have (Basic, Grow, Advanced or Plus), type a Store name (2 to 60 characters) and select Create.
- A dev store is a real Lulu store for building and testing themes and apps. Search engines are kept out and a sample catalog is added for you.
- The store address is made from the name, for example demo-studio-sandbox.lulu.us.com.
- Its storefront is always password-protected, and the password can't be turned off. It takes test orders only: no real payments, gift cards or store credit.
- A dev store can't go live and can't be transferred. To build a store for a client, choose Client transfer store instead (see “Follow one onboarding job from both sides”).
- You can have up to 250 dev stores. Delete ones you no longer need to make room.
- Every plan of your own app is free on your dev stores. Other apps' paid plans are free only if they are marked “Free for partners”.
- Storage is the Basic plan's: 100 GB of files, 50 GB of video, and 250 videos and 3D models.
- Dev stores are free and publish nothing to the Theme Store or App Store.
3. Open the store admin
On the store's row select Open admin. The store admin opens in a new tab and signs you in automatically. Preview opens the storefront instead.
- Open admin is a single-use sign-in link, so you never need the store's password.
- You enter as a Collaborator named after your partner account, not as the store owner, so the store's activity log shows your work.
- Use only demonstration products and customer details in a dev store.
4. Pick a built-in theme to start from
In the store admin select Online Store. The live theme is at the top; built-in Lulu themes are already installed under Draft themes. Choose the one closest to the design you want.
- Starting from a draft keeps the storefront stable while you work.
- You can add more free themes from the Theme Store link on the same page. A store holds up to 20 themes.
- A paid Theme Store theme stays a trial on a partner store: you can customise and preview it, but its code (custom.js and head snippets) is read-only and it can't be published. The client buys it after the transfer. Start from a free theme.
5. Build the theme in the theme editor
Select Edit theme on the draft. The same theme editor merchants use opens: sections and blocks on the left, a live preview in the middle, settings for the selected item on the right. Select Save when the preview looks right.
- Add, reorder, hide and configure sections and blocks for each page type.
- Theme settings hold the colours, typography, buttons, cards and layout rules for the whole theme.
- Custom CSS, custom JavaScript and head snippets live under the theme's “…” menu → Edit code.
- Open Preview and check the real storefront on a phone and a desktop, not only the editor preview.
6. Download the theme file
Back on Online Store, open the “…” (Theme actions) menu on your theme and select Download theme file. You get a zip named theme_export__<store>__<theme>__<date>.zip.
- shopwise-theme.json at the root of the zip is the main file Lulu reads when you upload it again. You can also edit config/settings_data.json, templates/*.json, config/groups.json and assets/custom.css: an edited copy is used, an untouched one changes nothing. sections/*.json, the READMEs, custom.js and head-snippets.html are for reading only (see “Theme package format reference”).
- Keep every zip you release: published packages have no stored history and no rollback.
- Liquid themes from other platforms are not Lulu packages and are refused.
7. Start a theme submission
In the partner portal select New submission on the Dashboard. Keep Theme selected at the top of the form.
- The form says it plainly: drafts stay private to you until you send them for review.
- Every theme and every app is reviewed by the Lulu team before it goes public.
8. Choose where the theme comes from
Select From a development store, then choose the Development store and the Theme. Or select Upload a file and choose your zip.
- From a development store: the theme is copied exactly as it is at that moment. Later edits in the store do not change the submission.
- Upload a file: a Lulu theme export zip or the shopwise-theme.json file on its own, 5 MB at most.
- A file that is not a Lulu theme is refused with a message saying why, and no draft is saved.
- Images uploaded in that store are copied into the package automatically.
- SVG images referenced by the theme are refused. Use PNG or WebP instead.
9. Fill in the theme listing details
Enter Theme name (up to 120 characters), a one-sentence Tagline (up to 200), Industries separated by commas (up to 10) and Price (USD). Then upload a Desktop screenshot (required, 1600×1000 recommended) and, optionally, a Mobile screenshot.
- Enter 0 in Price to offer the theme for free.
- Price is in US dollars.
- A paid theme is sold to merchants by Lulu at that one-time price. You receive a share of each sale; the live percentage is shown under the Price field and on the Program page, and it is paid with your partner payouts.
- Description, features, version and support details are added on the Listings page after approval; the screenshots you uploaded with the submission are carried over and can be replaced there.
- A desktop screenshot upload is required before you can submit. The mobile screenshot is optional.
10. Send the theme for review
Select Save and submit for review. Or select Save draft, check the draft, and then select Submit for review on its page.
- The submission page shows Listing details and a Theme package summary: the theme name inside the package, how many settings it carries, and whether sections and custom code are included.
- Once submitted, the submission is locked while the Lulu team reviews it.
- The Theme package summary reads, for example, "Settings: N values (preset defaults)", and lists the section names and any custom code.
- You can edit and delete a draft at any time.
- While a submission waits for review you can withdraw it. It goes back to draft and you can edit it again.
- After approval, merchants can install the theme from the admin Theme Store with Try theme, and from the public theme page with Log in to add.
11. Understand what an app is here
A partner app is published as an App Store listing at apps.lulu.us.com and inside every merchant's admin App Store, marked as a partner app. The portal takes the listing text; there is no field for code, a callback URL, permissions or billing plans.
- The store data an app may view or edit (its scopes) is shown to merchants on the install consent screen. Lulu sets these with you; the portal cannot.
- Paid app plans and storefront embeds are also configured by Lulu.
- Never upload app code as a theme package. Agree the technical integration with the Lulu team before you promote the app.
12. Propose an app listing
Select New submission, then App. Fill in App name (up to 120 characters), Tagline (up to 200), Category (up to 80), Pricing tag and Description (up to 5,000). All five are required.
- Category is free text, for example Marketing, Shipping or Store design.
- Pricing tag: type exactly one of Free, Free plan, Free to install or Free trial. Any other wording, including “Free plan available”, is published as Free.
- In Description say what the app does, who it is for, which store data it reads and writes, and what a merchant needs before it works.
13. Save the app draft and submit it
Select Save draft to check the proposal, then Submit for review on its page. Or select Save and submit for review straight away.
- A draft appears under Your submissions with the status Draft and is visible only to you.
- Once submitted it is locked while it is reviewed.
- You can edit and delete an app draft, and withdraw a submitted app back to draft while it waits for review.
14. Follow the review status
On the Dashboard, Your submissions lists every theme and app with its Type, Status, Created and Reviewed dates. Select a title to open it.
- Draft: private to you. Submitted: waiting in the queue. In review: a reviewer has picked it up.
- Approved: published. Rejected: the reviewer asked for changes.
- You are not emailed about a submission decision; check this list.
15. Act on a rejection
Open the rejected submission. Changes requested shows the reviewer's notes and the review date. Fix every point, then send a new submission.
- There is no resubmit button on a rejected submission; the corrected version is a new one.
- Keep the notes open while you prepare it so nothing is missed.
16. Find your published listing
After approval, open Listings in the top bar. The Themes tab and the Apps tab list what you own, with Type, Price or Pricing, and Visibility. View opens the public page.
- Approval published the listing automatically; there is no separate publish step for you.
- A new theme listing starts with the submission screenshots but without a description, so complete the next step before you promote it.
- Listing edits go live immediately and are not reviewed again. Treat every save as a release.
- For an app, add the app link and screenshots in Listings → Apps first. Merchants can install the app (Open app) only once these are in place.
17. Complete the theme listing
On the Themes tab select Edit on your theme. Fill in Name, Tagline, Description, Industries (select the chips), Features (comma-separated), Screenshot URL, Website, Price (USD, one-time) and Visibility, then select Save changes.
- Screenshot URL takes an https:// address of an image you host.
- Website becomes the developer link on your listing.
- Visibility Listed shows the theme in the Theme Store; Unlisted hides it straight away without deleting it.
18. Add release and support details
In the same form fill in Version (for example 1.0.1), Release date, Documentation URL, Changelog, Support email and Support URL, then select Save changes.
- Changelog takes one line per release: version | date | what changed, up to 30 lines.
- Merchants read this block before installing, and it is how existing merchants learn that something changed.
19. Update the published theme
Under Theme package choose one route. Upload zip replaces the package with a tested export. Or choose a store in Edit in development store and select Open editor, make your changes, then pick that store and theme in Update from development store and select Update listing.
- Select Download first to keep a copy of the package you are replacing.
- Open editor installs your published package on the dev store as a fresh draft and opens the theme editor; it publishes nothing by itself.
- An update reaches new installations only. Merchants who installed earlier keep their own copy and customisations; tell them through Version and Changelog.
20. Maintain the app listing
On the Apps tab select Edit on your app. Update Name, Tagline, Description, Category, Pricing, Icon (an emoji or an image URL), Website, Support email, Support URL, Privacy policy URL and Documentation URL, then select Save changes.
- Pricing is a list here: Free, Free plan available, Free to install or Free trial. It is a label, not a billing plan.
- Every web address must start with https://.
- Changing permissions, plans or code still goes through the Lulu team.
21. Use app version history
Every save of an app listing is recorded under Version history, newest first. To go back, select Restore on an earlier entry.
- Restore copies that version back and records it as a new version (“Restored from v<n>”); history is never rewritten.
- Stores stay on the version they installed until their owner selects Update in their admin, so a restore does not roll back every store.
22. Read and answer merchant reviews
Open Reviews and switch between the Apps and Themes tabs. Select Reply under a review, write your answer and select Post reply. Use Edit reply to change it later.
- Replies are public and show your account name under the review on the App Store or Theme Store.
- Keep replies about the issue raised; never post customer data, order details or passwords.
23. Ask a merchant for a review
In Request a review choose the Listing, type the merchant's email address in To, enter Your name and an optional Message, then select Send request.
- Only merchants who have your app installed, or your theme in their store, can write a review.
24. Work in a merchant's store with collaborator access
To help a merchant in their own store, ask them for the 4-digit collaborator request code from their admin under Settings → Users → Collaborators. On a lead in Leads, enter it as Collaborator request code and select Request access. Once they approve, the store appears under Client stores on your Dashboard with an Open admin button.
- You always enter as a Collaborator; the merchant can suspend or remove your access at any time.
- Your own dev stores and client transfer stores need none of this — they are already yours.
- Default access does not include exporting customers, orders or a store backup. Ask the store owner to turn on what the job needs under Settings → Users → Collaborators → "Edit access".
- Without the matching export permission you also can't create an API token or a webhook that reads customers or orders in that store.
- Access you don't use for 90 days is removed. You get a warning email after 75 days; open the store admin to keep it.
- After 5 wrong request codes for a store, requests to that store are locked for 60 minutes.
Completion checklist
- A dev store exists and opens from the Dashboard with Open admin.
- Your theme was built and checked on the real storefront, and you kept its zip.
- The theme submission and the app listing proposal were sent for review.
- After approval the theme listing has a screenshot, description, version, changelog and support details.
- The app's permissions, plans and integration were agreed with the Lulu team.
- You know how to update a theme package and restore an app version.
Troubleshooting
Create store says I have reached the limit.
You can have up to 250 dev stores. Delete dev stores you no longer need, then create a new one. Client transfer stores have no limit.
An app plan says "Not free on partner stores".
A paid app plan is free on your partner stores only if it is a free plan, a plan marked "Free for partners", or (on dev stores) a plan of your own app. Other paid plans show "Not free on partner stores" and can't be chosen; the store owner picks them after the transfer. On a dev store, every plan of your own app is free.
Open admin shows an error instead of the store.
The single-use link may have been used already; select Open admin again. For a client store, the merchant may have suspended your collaborator access, which only they can restore.
My theme upload was refused.
Only a Lulu theme export (a zip containing shopwise-theme.json, or that file alone) up to 5 MB is accepted. Download it again from Online Store → “…” → Download theme file and upload that file.
My later edits are not in the submission.
A submission is a snapshot taken when you saved it. Send a new submission, or after approval update the listing from Listings → Theme package.
My app shows as Free although I typed a different pricing tag.
Only Free, Free plan, Free to install and Free trial are recognised when an app is published. After approval, correct it with the Pricing list on Listings → Apps → Edit.
Where do I upload my app code or set its permissions?
Nowhere in the portal. It publishes the listing only. Agree the integration, the store data it needs and any paid plans with the Lulu team.
An existing merchant did not get my theme update.
Installed themes are the merchant's own copies and are never overwritten. Updates reach new installations; describe the change in Version and Changelog so existing merchants can decide to reinstall.
How do I take my theme out of the Theme Store?
Open Listings → Themes → Edit, set Visibility to Unlisted and select Save changes. For an app listing, contact Lulu support: apps cannot be unlisted from the portal.
Edit a theme package and submit it to the Theme Store
Download a theme package from your dev store, change its design settings, page layouts and CSS in the zip, upload it as a submission, check which edits were used, preview it, and get it approved for the Theme Store.
Illustrated guide: lulu.us.com/help/guide-partner-theme-packages
Before you startYou need an approved partner account and a dev store (see “Build apps and themes from start to finish”). The easiest way to make a theme is still to design it in the real theme editor on your dev store and submit it with “From a development store”. Editing the zip is for changes you prefer to make in files, or for moving a theme between stores. A package carries design settings, the section layout of every page, the header, footer and password page, and custom CSS, JavaScript and head snippets. It can't add new section types or carry image files: images must already be uploaded to your dev store, and they are copied automatically.
1. Download the package
Open your dev store's admin, go to Online Store → Themes, open the “…” menu on the theme and choose “Download theme file”. You get a zip. Built-in themes such as Crave can only be downloaded once they are in one of your stores: add the theme to your dev store first, then download it from there.
2. Know which files you can edit
Unzip the package. These files are read back when you upload it:
- shopwise-theme.json: the main file. It holds name, settings, customCss, sections, codeFiles and presetKey, plus a “shopwise” block. Keep “version” at 1 (that is the file format). Put your own theme version in “themeVersion”, for example "2.0.0" (numbers and dots only, up to 20 characters).
- config/settings_data.json: design settings (colours, fonts, spacing) under “current”. A setting you delete goes back to the preset's default.
- templates/index.json, product.json, collection.json, cart.json, blog.json, search.json, page.json and suffix templates such as page.contact.json: the sections on each page, as {"sections": {…}, "order": […]}.
- config/groups.json: header, footer and password page.
- assets/custom.css: your extra CSS.
- sections/*.json and the README files are reference only and are never read back. Use sections/ to see which section types exist.
- custom.js and head snippets are only read from codeFiles inside shopwise-theme.json.
3. Make your changes
Edit either the main file or the separate files. Each export records a fingerprint of every separate file, so the upload can tell which ones you changed. A file you didn't touch is ignored. If you change the same thing in both shopwise-theme.json and a separate file, the main file wins and the upload warns you. Re-formatting a file (spacing, key order) doesn't count as a change.
- Example: change the colours in config/settings_data.json → current, re-order or add sections in templates/index.json using types listed in sections/, add CSS to assets/custom.css, and set "themeVersion": "2.0.0".
- Section types that don't exist are left out and listed after upload.
- Hidden blocks stay hidden when you edit a template.
- An emptied template file is skipped (with a warning), so you can't clear a page by uploading an empty file.
4. Zip it again
Zip the files again. A wrapping folder inside the zip is fine, and so are the extra files macOS adds. Keep the zip under 5 MB and include only one theme.
5. Upload it as a new submission
In the partner portal, select “New submission” on the Dashboard, choose a theme, pick the upload option and select “Upload a file”. Fill in the listing details and screenshots, then save. If the file can't be read, the page says exactly why: the JSON position of a syntax error, a missing shopwise-theme.json (with the list of files it found), two themes in one zip, or a changed “version” number. Fix it and choose the file again. You don't need to reload the page.
6. Check which edits were used
The submission page lists “Your edits to these files were used: …” and any warnings, such as settings or section types that were left out. The “Theme package” card shows the theme name, preset, how many settings differ from the preset, the sections on the home page and the version. If you edited the home page, Sections no longer says “stock default layout”.
7. Preview it
On the submission page, select “Preview in a development store”, then “Open in theme editor”. A new draft theme named after your submission opens in the real theme editor on your dev store, where you can look at every page. This works for drafts and for submissions waiting for review.
8. Fix and upload again
While the submission is a draft, use “Upload a new package” on the submission page to replace the file. The listing details stay as they are. If you already submitted it, select “Withdraw submission” first. That turns it back into a draft you can change.
9. Submit for review and get approved
Use “Save and submit” (or submit from the draft). If the submit step fails, the submission page shows the reason, for example a missing screenshot. When the Lulu team approves it, the theme is published on the Theme Store with your screenshots and the version from themeVersion, and buyers install exactly the package you submitted. After approval, the Listings page lets you download the package, upload a new zip, open the editor, or sync from your store.
- A Theme Store “View demo” button is not available for partner themes yet. Buyers see your screenshots.
Completion checklist
- The package was downloaded from your dev store with “Download theme file”.
- “version” in the shopwise block is still 1, and themeVersion looks like 2.0.0.
- The upload shows “Your edits to these files were used” for the files you changed.
- The preview in your dev store looks the way you expect.
- Screenshots are attached before you submit.
Troubleshooting
The upload says the package is for a newer version of the platform.
You changed “version” in the shopwise block. That number is the file format: set it back to 1 and put your theme's version in “themeVersion” instead.
My theme still looks like the original after uploading.
Check the list of used edits on the submission page. A file with no changes from the export is ignored. If you edited both shopwise-theme.json and a separate file for the same thing, the main file wins. Packages downloaded before 9 October 2026 have no fingerprints, so their separate files are ignored: download a fresh package and apply your changes to it.
The upload says it looks like a Shopify theme export.
Shopify themes (Liquid files) can't be uploaded. Use a package downloaded from a Lulu store.
Choosing the same file again does nothing.
After a failed upload the file field is cleared, so choose the file again. If you edited the file after choosing it, choose it again too.
Some sections or settings were “left out”.
Only section types that exist on the platform (listed in sections/) and settings the theme knows can be imported. Rename them to existing ones, or build the layout in the theme editor instead.
Theme package format reference
Every file and key in a theme package (shopwise-theme.json, config/groups.json, templates), its type and limit, which section types each presetKey offers, fonts, images, CSS hooks, custom.js, and what the format cannot do.
Illustrated guide: lulu.us.com/help/guide-theme-package-format
Before you startThis is the reference for the files inside a theme package. For the step-by-step upload and submission flow, read “Edit a theme package and submit it to the Theme Store” first. Everything here comes from the platform code: anything the platform doesn't recognise is dropped on upload, never stored. The same tables are in your dev store's admin under Online Store → Developer docs, generated live from the code.
1. The package and what is read back
A package is a zip (5 MB at most) or the shopwise-theme.json file on its own. On upload, Lulu reads shopwise-theme.json plus the copies of the same data you edited: config/settings_data.json, templates/*.json, config/groups.json and assets/custom.css. Each export stores a fingerprint of those copies in shopwise.derived, so an untouched copy changes nothing and an edited copy replaces the matching part of shopwise-theme.json. If you edit the same part in both places, shopwise-theme.json wins.
- Read back: shopwise-theme.json, config/settings_data.json (only its “current” object), templates/*.json, config/groups.json, assets/custom.css.
- Never read back: config/settings_schema.json, sections/*.json, README.md, README.txt, assets/custom.js and snippets/head-snippets.html. Custom JavaScript and head snippets come only from codeFiles in shopwise-theme.json.
- shopwise-theme.json can sit at the root of the zip or one folder down. Two copies at the same depth are refused.
- A package downloaded before 9 October 2026 has no fingerprints: only shopwise-theme.json is used; edited copies are ignored and the upload names them.
- Re-formatting a file (spacing, key order) is not an edit. An emptied template file is ignored: hide sections with "disabled": true instead.
- Every value goes through the same checks as a save in the theme editor, so a package can't store anything the editor couldn't.
2. Add a package from GitHub
Instead of uploading a zip, you can keep the package in a GitHub repository. In your store admin, go to Online Store → Import and choose Add from GitHub.
- Repository URL: https://github.com/owner/repo, or just owner/repo. Only repositories on github.com can be added.
- Branch: leave it blank to use main.
- Subfolder: the folder that holds shopwise-theme.json, for example themes/aurora. Leave it blank when shopwise-theme.json is at the top of the repository.
- Personal access token: only needed for a private repository. Create a fine-grained token with read-only access to that repository’s Contents. It is used for that one download and never saved, so you paste it again each time you sync.
- Only the package’s text files are read (shopwise-theme.json, config/, templates/, assets/custom.css and the like). Images, fonts and other files in the repository are skipped. The download can be up to 50 MB; the package files in it have the same 5 MB limit as a zip upload.
- The theme is added as a draft with a GitHub label. To pull the latest commit later, open the theme’s … menu and choose Sync from GitHub. Sync replaces the theme’s settings, sections and code with the files on GitHub, and saves what was there before in the theme editor’s History so you can roll back. Syncing the live theme asks you to confirm first, because customers see the change right away.
- Disconnect from GitHub, in the same menu, keeps the theme as it is and stops syncing.
3. shopwise-theme.json: top-level keys
The main file is a JSON object. A {"snapshot": {…}} wrapper around the same keys is also accepted.
- name (text): the theme name, up to 255 characters. If the store already has a theme with that name, “(imported)” is added.
- settings (object): design settings, key = setting name, value = text. Only the 55 known settings are kept; an unknown name or a value outside its range is dropped. See “settings”.
- customCss (text): theme-wide CSS, up to 20,000 characters. A literal </style> is escaped; nothing else is changed.
- sections (object or null): every page layout plus the header, footer and password page. null means the stock home page layout and empty templates. See “sections”.
- codeFiles (object): {"customJs": text up to 100,000 characters, "headSnippets": text up to 20,000 characters}. Other keys are dropped.
- presetKey (text): the base theme your package builds on. It picks the default colours and fonts and which section types the editor offers. See “presetKey”.
- shopwise (object): format information. version (number, must be 1: it is the file format, not your theme's version), themeVersion (your version, 1 to 4 dot-separated numbers such as 2.0.1, up to 20 characters; anything else is ignored with a warning), kind, exportedAt, store, themeId, name, source, presetKey (a copy for reading; the top-level presetKey is the one used), provenance {catalogKey, listingId} and derived (the file fingerprints, don't edit them).
4. settings: design settings
settings holds design tokens such as "--s-accent": "#0a5c46". There are 55 of them, in the groups Colors, Typography, Layout, Buttons, Cards, Forms, Icons, Animations and Responsive; config/settings_schema.json in your package and Online Store → Developer docs list each one with its type and range.
- color: #RGB, #RRGGBB or #RRGGBBAA.
- size: whole pixels such as "14px", within the setting's minimum and maximum.
- percent: such as "80%", within the setting's range.
- select: one of the setting's listed values.
- font: a font id from the font list (see “Fonts”). "theme" is not stored: leave the setting out to use the preset's own font.
- A setting you leave out uses the preset's default. In config/settings_data.json, “current” replaces all settings, so deleting a key there also resets it.
5. sections: page layouts
sections has these keys. Each section is {"id", "type", "settings", "blocks"?, "hidden"?}; ids are 1–40 letters, digits, _ or - (anything else gets a new random id). Blocks are {"id", "type", "settings", "hidden"?, "blocks"?} and nest at most 3 levels, 80 blocks per section in total.
- home (list, required when sections is not null): home page sections, up to 40, of any registered section type.
- templates (object): product, collection, cart, blog (blog list and articles), search and page, each a list of up to 15 sections. Any type except announcement-bar. A template section with "area": "top" renders above the page's own content (in templates/*.json that is "shopwise_area": "top").
- pageTemplates (object): alternate page templates, key = suffix such as "contact" (lowercase letters, digits and -, up to 40 characters), up to 20 of them, each a list like templates.page.
- resourceTemplates (object): {"product": {suffix: list}, "collection": {…}, "post": {…}} — alternate product, collection and blog-article templates. Suffix: lowercase letters, digits and -, up to 25 characters; up to 20 per type.
- templateCore (object): settings of each template's built-in layout (product gallery and buy box, collection grid, cart, blog, search, page) — keyed product, collection, cart, blog, search, page. It is only in shopwise-theme.json, not in templates/*.json.
- headerGroup, footerGroup, passwordPage: see the next step. They are also in config/groups.json.
- Unknown section types and setting keys are left out and listed after the upload (on the submission page, or on the Themes page after Online Store → Import). The section types that exist are the sections/ folder of any package and the Section library in Developer docs.
6. config/groups.json: header, footer, announcement bar and password page
config/groups.json is {"headerGroup", "footerGroup", "passwordPage"}. A group you include replaces that whole group; a group you set to null is left as it is in shopwise-theme.json.
- headerGroup.settings: 95 header settings (logo, menu, search, icons, sticky, transparent header, colours, customCss). headerGroup.blocks: up to 6 blocks of type text, icon, image, button, custom-html, shown beside the header icons.
- Header layout and icons, so each theme can have its own header: menuRow top | bottom | above (above = the menu on the first row, logo and icons on the row under it), logoPosition left | center, menuPosition left | center | right, utilitiesPosition right | split (split = search icon at the left, the other icons on the right), accountIcon person | circle | round | square, cartIcon bag | cart | tote | basket | cart-outline, wishlistIcon heart | bookmark | star, searchIcon magnifier | text, iconSize small | standard | large. Unknown values fall back to the default.
- headerGroup.announcementBar: {"settings", "blocks"}. Up to 10 blocks: announcement (text, textMobile, link, newTab, scheme, startAt, endAt; startAt/endAt schedule it) and utility-link (role, label, link, newTab, icon, iconOnly). headerGroup.announcement {enabled, text, link} is the older single-message bar, used only while announcementBar has no blocks.
- footerGroup.sections: up to 6 sections above the footer, of type newsletter, rich-text, trust-badges, brands, multicolumn, text, icons-with-text, divider, marquee, contact-form, contact-info, location-map, offer-popup, stickers, scroll-to-top, age-verifier, popup.
- footerGroup.settings: the classic footer (menus, newsletter, social icons, payment icons, copyright, columns, colours, customCss). footerGroup.blocks: up to 8 social links (platform, url, label, iconImage).
- footerGroup.layoutBlocks: the block-built footer. Empty or missing means the classic settings footer is used. Up to 24 top-level blocks and 80 blocks in total. Types: group, heading, text, image, logo, button, menu, links, social, email-signup, payment-icons, copyright, policy-links, divider, jumbo-text. A group holds up to 12 children of any of those types (groups nest up to 3 levels); a links block holds up to 8 link children.
- passwordPage.settings: heading, message, backgroundImage, logoImage, passwordLabel, buttonLabel.
7. Add product, collection and page templates
To add a template, add a file to templates/ and upload the package. A file you add counts as an edit, so it is used.
- Shared templates: templates/product.json, collection.json, cart.json, blog.json, search.json, page.json. Home is templates/index.json.
- Alternates: templates/page.<suffix>.json (for example page.contact.json), templates/product.<suffix>.json, templates/collection.<suffix>.json and templates/article.<suffix>.json (stored as resourceTemplates.post).
- File shape: {"sections": {"<id>": {"type", "settings", "blocks"?, "block_order"?, "disabled"?}}, "order": ["<id>", …]}. Copy an exported file as a starting point.
- A template file with no sections is ignored. You can't remove a template by uploading a package: delete it in the theme editor.
- A page, product, collection or article uses an alternate template once the merchant picks it under Theme template in its editor. That list shows the templates of the LIVE theme.
8. presetKey: the base theme and its section palette
presetKey must be the id of a registered preset. It decides the default colours and fonts underneath your settings, and which section types the editor's “Add section” list offers. It does not remove sections: any registered section type in your package is kept and keeps rendering even if the preset doesn't offer it. An unknown presetKey is ignored and the upload warns you, listing the valid keys; the theme then gets the default (Horizon) colours and fonts unless its name matches a preset, and the full section list.
- Core sections, offered by every preset: announcement-bar, newsletter, offer-popup, popup, stickers, scroll-to-top, age-verifier, hero, image-banner, image-with-text, video, slideshow, gallery, image-hotspots, featured-collection, collection-list, featured-product, recommended-products, product-highlight, product-hotspots, bundle-offer, product-compare, specifications, rich-text, faq, multicolumn, text, divider, icons-with-text, contact-form, contact-info, location-map, blog-posts, collapsed-rows, testimonials, trust-badges, brands, custom-html.
- Always offered as well (app sections): app-block, presale-banner, bb-canvas, ad-slot, foryou-row.
- Presentational sections that differ per preset: ribbon-banner, content-carousel, editorial, video-banner, video-with-text, pull-quote, marquee, jumbo-text, image-compare, stats-counter, section-tabs, testimonial.
- Full library (all 56 section types, including marketplace-discovery): horizon, ignite, vertex, splendor, atelier, circuit. Every paid Theme Store preset key, and a missing or unknown presetKey, also get the full library.
- dawn (Dawn): core + content-carousel, editorial, image-compare, stats-counter, section-tabs, video-banner, video-with-text.
- craft (Craft): core + editorial, pull-quote, content-carousel, image-compare, marquee, video-with-text.
- sense (Sense): core + editorial, content-carousel, image-compare, stats-counter, section-tabs, video-with-text.
- refresh (Refresh): core + jumbo-text, marquee, ribbon-banner, video-banner, content-carousel, pull-quote.
- studio (Studio): core + editorial, pull-quote, content-carousel, image-compare, section-tabs, video-with-text.
- colorblock (Colorblock): core + marquee, jumbo-text, ribbon-banner, video-banner, content-carousel, stats-counter.
- publisher (Publisher): core + editorial, pull-quote, jumbo-text, content-carousel, section-tabs, marquee.
- crave (Crave): core + ribbon-banner, marquee, video-banner, video-with-text, content-carousel, stats-counter.
- flow (Flow): core + editorial, marquee, content-carousel, image-compare, stats-counter, video-with-text.
- voyage (Voyage): core + editorial, pull-quote, content-carousel, image-compare, video-with-text.
- impulse (Impulse): core + jumbo-text, marquee, ribbon-banner, video-banner, content-carousel, pull-quote.
- instance (Instance): core + content-carousel, editorial, stats-counter, section-tabs, ribbon-banner, video-with-text.
- satin (Satin): core + editorial, pull-quote, content-carousel, image-compare, video-banner.
- forest (Forest): core + editorial, pull-quote, content-carousel, image-compare, marquee, video-with-text.
- composition (Composition): core + jumbo-text, marquee, editorial, content-carousel, stats-counter, video-banner.
- pristine (Pristine): core + editorial, content-carousel, image-compare, stats-counter, video-with-text.
- loft (Loft): core + marquee, ribbon-banner, jumbo-text, content-carousel, editorial, video-with-text.
- noom (Noom): core + editorial, pull-quote, content-carousel, video-banner, video-with-text, image-compare.
- igloo (Igloo): core + marquee, ribbon-banner, content-carousel, stats-counter, video-banner, image-compare.
- Paid Theme Store preset keys (for example prestige) are valid too, but they can mark your draft as that paid theme, and publishing it then needs the purchase. Use a free preset key for your own theme: horizon, vertex, dawn, craft, sense, refresh, studio, colorblock, publisher, crave, flow, voyage, impulse, instance, satin, forest, composition, pristine, loft, noom, igloo. ignite, splendor, atelier and circuit exist for existing themes and paid listings.
- Changing presetKey (for example crave to composition) changes both the section palette and the default look; set colours and fonts in settings if you want them fixed.
9. Fonts
The Heading font and Body font settings take one of 12 catalog fonts: system (System sans), inter (Inter), poppins (Poppins), sora (Sora), space-grotesk (Space Grotesk), assistant (Assistant), nunito (Nunito), lato (Lato), fraunces (Fraunces (serif)), cormorant (Cormorant (serif)), spectral (Spectral (serif)), georgia (Georgia (serif)). A theme can't add fonts to that list: the list is part of the platform code.
- Weights each catalog font loads: Inter, Poppins and Fraunces 400 to 900; Nunito 400 and 600 to 900; Sora, Assistant and Spectral 400 to 800; Lato 400, 700 and 900; Space Grotesk 400 to 700; Cormorant 500 to 700. A weight setting heavier than the font has (for example 800 on Space Grotesk) shows as its heaviest weight.
- The preset's own pair (the “Theme default” choice) can be a font outside the catalog, for example Barlow on Vertex or Figtree on Atelier. Leave the font settings out to use it.
- For another font, add a Google Fonts or Fontshare stylesheet link in head snippets (codeFiles.headSnippets) and set font-family in customCss. Other font hosts are blocked by the storefront's content security policy. Such a font never appears in the Typography picker, and because your CSS sets the font directly, a catalog font a merchant picks there won't replace it.
10. Images
A package never contains image files. Image settings (and url(...) in CSS) hold an address: a path on the store such as /media/stores/<id>/media/<file>, or any https:// address (up to 500 characters).
- Images uploaded to a store are only served on that store. Imported into another store with Online Store → Import, they don't show (they can still show to you while you are signed in to the store they came from).
- Theme Store packages: when you submit a theme, upload a package to your listing, or update the listing from a development store, images from your own dev stores are copied into the listing's package and the addresses are rewritten, so they show in the Theme Store demo and on every store that installs the theme. At most 200 images and 100 MB; JPG, PNG, WebP, GIF, AVIF, MP4 or WebM only. SVG is refused: the upload stops and names the file to replace.
- Images on a public https:// address are used as they are and show everywhere.
- Store content (products, collections, menus, blog posts, pages) is never in a package; an installed theme shows the installing store's own.
11. CSS: theme-wide and per section
customCss (20,000 characters) is added after the theme's own styles on every storefront page. Each section, the header, the footer and the announcement bar also have their own customCss setting of up to 4,000 characters.
- Per-section CSS is scoped: it is wrapped in that section's [data-sw-sec="<section id>"] selector with CSS nesting, so h2 { … } only styles that section's headings. Header, footer and announcement-bar CSS are scoped to [data-sw-hdr], [data-sw-footer] and [data-sw-ann] the same way.
- In per-section CSS, @import and expression( are removed, a stray } is dropped and unclosed rules are closed, so it can't escape its section.
- Stable hooks: every section carries .sw-<type> (for example .sw-rich-text) and every shared block carries .sw-block-<type> (for example .sw-block-heading). They come from the type name and are the documented classes to target.
- data-section-id="<id>" is on every section wrapper. The id stays the same across saves but a duplicated section gets a new one, so prefer .sw-<type>.
- Other classes, such as .s-header, .pc (product card) or .s-btn, are internal. Existing markup is kept stable on purpose, but these names are not a published contract and can change. Design tokens (var(--s-accent) and the other settings) are the safest thing to build on.
12. custom.js and head snippets
codeFiles.customJs runs once per full page load, at the end of <body>, on storefront pages only. Moving between storefront pages happens without a page reload and does not run it again, and there is no platform event after a section renders or a page changes.
- To react to new content, use a MutationObserver on document.body.
- Events you can listen for: sw:consent on window (cookie choice changed), sw:wishlist:change on document (Wishlist Plus), sw:quickview:open, sw:quickview:close and sw:quickview:add on document (Quick view).
- Tracking code (Google, Meta, TikTok and similar) waits for the visitor's cookie consent. Wrap other tracking in window.swPixel('analytics' or 'marketing', function () { … }).
- headSnippets is split into individual meta, link, base, script and style tags in <head>.
13. What a theme can't do
Themes are configuration for one shared storefront engine. A package can't contain Liquid, section source code or new section types, and Liquid support is not planned (it is an open owner decision, not on the roadmap).
- Your own markup: use the Custom HTML/Embed section (custom-html, offered by every preset, up to 20,000 characters) or the Custom HTML block in the header. The HTML renders as written, but <script> tags inside it don't run: put scripts in custom.js.
- Edit code in the admin offers custom.css, custom.js and head-snippets.html. settings.json and sections.json there are read-only views.
- No translation files, no layout files, no image files.
14. Updates after merchants install your theme
Installing a Theme Store theme creates a separate draft copy in the merchant's store. When you upload a new package or sync from your dev store, new installs get the new version. Copies already installed are never changed, so a merchant's own edits are never overwritten — and they don't receive your update either.
- There is no update notice or merge. A merchant who wants your new version installs the theme again (a new draft) and moves their changes across.
- Keep each released package and its themeVersion: the platform keeps no release history for a listing.
Completion checklist
- shopwise.version is 1 and themeVersion looks like 2.0.1.
- presetKey is a free preset id whose section list contains every section type you use.
- Fonts are catalog ids, or the preset's own pair.
- Images are on your dev store or on a public https:// address, none of them SVG.
- After uploading, the submission page lists the files you edited and no unexpected warnings.
Troubleshooting
A section disappeared after upload.
Its type isn't registered, so it was left out. Use a type from the sections/ folder of a downloaded package. A section type that exists but isn't in your preset's list is kept; it only doesn't appear in “Add section”.
My presetKey change did nothing.
An unknown presetKey is ignored, and the upload warns you with the list of valid keys. Use one of them. Remember that the top-level presetKey is used, not the copy inside the shopwise block.
Images are blank on another store.
They are links to images uploaded to the store the theme came from. Upload the images in the new store and choose them again, or use public https:// addresses. Theme Store submissions, listing uploads and listing updates from a development store copy dev-store images for you.
My edit to custom.js in the zip was ignored.
assets/custom.js and snippets/head-snippets.html are never read back. Edit codeFiles in shopwise-theme.json.
Add from GitHub says it couldn’t find the repository or branch.
Check the spelling of owner/repo and the branch name. A private repository needs a personal access token with read access to its Contents — without one, GitHub answers as if the repository didn’t exist. Tokens are never saved, so a private repository asks for one on every sync.
Become an onboarding partner — and how the platform approves you
For agencies and freelancers who set stores up for merchants: apply for a partner account, build your onboarding profile, submit it for review, and see how the Lulu team approves, asks for changes, publishes, unlists or suspends it.
Illustrated guide: lulu.us.com/help/guide-onboarding-partner-apply
Before you startOnboarding partners are agencies and freelancers who set stores up for Lulu merchants: theme and design, products, payments, shipping, migration — everything until the store is live. Merchants find you in the public partner directory at partners.lulu.us.com/experts and send you requests, and you answer them in the partner portal. Merchants can pay for your packages and offers through Lulu — the payment is held until they accept your work and the platform keeps a commission — so a request is never a reason to ask for payment outside the platform. Anyone with a business email can apply, and there are two approvals: first the Lulu team approves your partner ACCOUNT (the same account app and theme developers use), then it reviews your public ONBOARDING PROFILE before it appears in the directory. Steps marked "Partner:" are done by you in the partner portal; steps marked "Admin:" are done by a platform administrator in the platform console at app.lulu.us.com/super. Have ready: your business name, a square logo (JPG, PNG or WebP, up to 5 MB), an optional wide cover image, a short description of what you do, and the price of at least one package. The screenshots come from a demonstration account called "Demo Onboarding Studio".
1. Partner: Create a partner account
Go to partners.lulu.us.com/partners and click the "Create account" tab. Enter "Your name or company", your "Email" and a "Password" of at least 8 characters, then click "Apply for a partner account". You are signed straight in to your application and we email you a link to verify your address. There is no separate signup for onboarding partners: you use the same partner account as app and theme developers, and you choose the onboarding work later by creating an onboarding profile. Applying is free.
- Use an email address you read — every decision and every merchant request is emailed.
- Use your business name as it should appear to the Lulu team; merchants see the name you set on your profile later.
2. Partner: Complete and submit your application
On "Your partner application", choose the Partner Program, the Reseller Program or both, then enter your legal name, whether you apply as a business (with its registration number) or as an individual, your address and country, a contact name and phone number, and your relevant experience; a website is optional. Resellers also add the support contact customers should use and confirm they completed the reseller training. Open the link in the verification email, read and accept the program agreement, then click "Submit application". You receive an email confirming we received it; our team reviews every application by hand, usually within one to two business days. Joining the Partner Program has no minimum number of customers. The Reseller Program needs at least 10 active attributed stores before you can apply, unless our team invites you; until then "Reseller Program" can't be ticked and the page shows your count.
3. Partner: Answer a request for information
If we need more details, you receive an email "More information needed" and the application shows "Information requested" with what we need. Sign in, answer in "Your answer to our request" and click "Send response". You get an email when the application is approved or not approved. While it is in review, signing in opens your application, not the partner dashboard.
4. Admin: Approve the partner account
Platform administrators receive an email when an application is submitted or answered. In the platform console open "Partners" → "Applications", click "Review", check the organisation, agreement and (for resellers) the training, then choose Approve, Request information or Reject and write the reason. The reason stays internal; only the message you write for the applicant is emailed.
- Filters: Awaiting approval, Active, Suspended, Rejected, All.
- A rejected application can still be accepted later with "Approve after all".
5. Partner: Sign in and open your onboarding profile
Once approved, sign in at partners.lulu.us.com/partners. The Dashboard starts with the "Onboarding profile" card: its status, your starting price, new requests and your rating. Click "Create profile" (or "Edit profile" once you have started), or use "Onboarding profile" in the top menu.
- Also on the Dashboard: "Client stores" (merchant stores you were given access to) and "Stores" (your dev stores for building and testing, and client transfer stores you build for a client and transfer).
6. Partner: Start your profile
On the Onboarding profile page, enter the "Business name" merchants should see and click "Create profile". The profile starts as a Draft: nothing is public until the Lulu team reviews it.
7. Partner: Fill in the basics
Under "Basics" complete the "Business name", the "Page address" (partners.lulu.us.com/experts/your-address — lowercase letters, numbers and hyphens, 3 to 40 characters), a one-line "Tagline" (at least 10 characters, up to 160) and "About" (at least 80 characters: what you do, who you do it for, how you work). The status box at the top lists what is still missing before you can submit.
- The page address can only be changed while the profile is a draft; it is fixed once the profile has been reviewed.
- Some platform words cannot be used as an address; the page tells you if one is reserved.
8. Partner: Add your logo, cover image and services
Under "Logo & cover" click "Upload" to add a logo (required) and, optionally, a wide cover image — JPG, PNG or WebP up to 5 MB. Under "What you do" tick every service you genuinely deliver: Store setup & launch, Theme & design, Custom development & apps, Migration, Payments, shipping & taxes, Marketing & SEO, Content, photo & branding, Training & ongoing support. Merchants filter the directory by these. Then pick up to 4 "Industries" and every "Languages" you work in.
9. Partner: Add contact details, team and social links
Under "How merchants reach you" enter the "Contact email" (every new request is emailed here) and, if you like, "Website", "Phone", "WhatsApp", plus "City" and "Country" — merchants can filter by country. Under "Your team" choose the "Team size", the optional "Founded" year, your "Typical response time" and whether you are "Taking on new clients" ("Not right now" keeps the page live but marks you as unavailable). "Social links" are optional. Click "Save".
- Links must start with http:// or https://.
10. Partner: Show your work
Open "Work" in the top menu and click "Add your first piece" (later "Add work"). Upload a "Screenshot" (landscape works best), give it a "Title", describe "What you did" and add either the Lulu store address or a "Link" to the live site or case study. Click "Add work". You can show up to 6 pieces; they appear as "Recent work" on your public page.
11. Partner: Add at least one package
A profile cannot be submitted without at least one active package. Open "Packages", click "Add your first package", give it a title, a price ("Fixed price", "Starting at" or "On request") and what is included, then click "Add package". The cheapest active package becomes the "From" price on your directory card. Creating and ordering packages is covered in detail in the guide "Create onboarding packages and get merchants onboarded".
- Every package has a minimum price, shown as helper text under the price field. For a free consultation use the "On request" price type.
12. Partner: Submit the profile for review
Back on "Onboarding profile", save any changes first ("Submit for review" stays disabled while there are unsaved changes). When the checklist is complete — business name, tagline, About of 80+ characters, at least one service, at least one package, a contact email and a logo — click "Submit for review".
- If your partner tier does not yet allow a directory listing, the page shows Request invitation instead. Click it once the checklist is complete.
- The Lulu team reviews each request and either invites you or declines. You are emailed either way.
13. Partner: While your profile is in review
The status changes to "In review": "Your profile is with the Lulu team. You can keep editing; we'll email you when it is decided." The page address is now fixed. The platform administrators receive an email "Partner profile for review — <your business name>".
14. Admin: Review the onboarding profile
In the platform console open "Partners" and go to "Onboarding profiles". The badge shows how many are awaiting review; the "Submitted" filter lists them with the profile name and page address, the partner account, the number of packages and leads, and the status "Awaiting review". Click "View" on published profiles, or open partners.lulu.us.com/experts/<address> after publishing, to see the public page. Check the name, About text, logo and packages for accuracy and for anything misleading.
- Filters: Submitted, Published, Rejected, Unlisted, All.
15. Admin: Ask for changes with a note
If something needs fixing, click "Reject". In "Reject onboarding profile" write "What needs to change" — a note is required, and it is emailed to the partner and shown in their portal — then click "Reject profile". The partner receives "About your Lulu onboarding profile".
- Be specific: say which field to change and why.
16. Partner: Fix what was asked and submit again
The profile shows "Changes needed" with the "Reviewer note". Make the changes, click "Save", then click "Submit for review" again. The reviewers are emailed "Partner profile updated — <name>".
17. Admin: Publish the profile
When the profile is ready, click "Publish" in the "Onboarding profiles" list. The console confirms "Profile published — it is live on the partner directory" and the partner receives "Your Lulu onboarding profile is live". Published profiles offer "Feature" (shown first, with a Featured badge), "Unlist" and "View".
- "Publish" also works for a profile that was rejected or unlisted earlier.
18. Partner: Your profile is live
The status is now "Published": "Live in the partner directory. Merchants can find you and send requests." Click "View public page" to see it. Changing the business name, About, logo, cover image or website sends a published profile back to review; everything else, including packages, updates straight away.
- To hide yourself temporarily, click "Unlist". Nothing is lost; click "Submit for review" when you want to be listed again.
19. Partner: Check your public page
Your page at partners.lulu.us.com/experts/your-address shows your cover and logo, "Taking new clients", tagline, rating, where you are based, how fast you reply, your starting price, languages and team size, then About, What they do, Packages, Recent work, Reviews from merchants and the "Request a quote" form.
20. Admin: Feature, unlist or suspend later
Platform administrators can manage a partner at any time from the same page. In "Onboarding profiles", "Unlist" hides a published profile from the directory (the partner can resubmit it), and "Feature"/"Unfeature" controls the Featured badge. In "Partner accounts", "Suspend" signs the partner out, blocks sign-in and hides their profile from the directory; "Reactivate" restores the account. Every decision is recorded in the audit log.
- The platform's own first-party onboarding team cannot be suspended.
Completion checklist
- Your partner account is Active and you can sign in at partners.lulu.us.com/partners.
- Your onboarding profile shows Published and "View public page" opens partners.lulu.us.com/experts/your-address.
- Your profile has a logo, a tagline, an About of at least 80 characters, at least one service and at least one active package.
- Your contact email is correct — new requests are emailed there.
- Admins: the profile appears under Onboarding profiles → Published, and nothing is left under Submitted.
Troubleshooting
I can't sign in: it says my application is still under review.
Your partner account has not been approved yet. Wait for the email "Your partner account is approved", usually within one to two business days. If it takes longer, contact support with the email address you applied with.
"Submit for review" is greyed out.
Either you have unsaved changes (click "Save" first) or the checklist under the status is not complete. Every item must be done, including at least one active package on the Packages page and an uploaded logo.
I can't change my page address.
The address can only be edited while the profile is a draft. Once it has been reviewed it is fixed, so links merchants have saved keep working. Contact support if it must change.
My published profile went back to "In review".
Changing the business name, About text, logo, cover image or website on a published profile sends it back for review. Your page stays out of the directory until the Lulu team publishes it again. Packages, contact details, services and availability do not trigger a review.
My profile was rejected. What now?
Open Onboarding profile, read the "Reviewer note" under "Changes needed", fix the points, click "Save" and then "Submit for review" again.
Admin: a profile does not appear in the directory after publishing.
A profile is public only when it is Published AND the partner account is Active. Check the partner's row under "Partner accounts"; a suspended account hides the profile until you click "Reactivate".
Create onboarding packages and get merchants onboarded
For approved onboarding partners and the merchants who hire them: create and order packages, how merchants find you and send a request, working your leads inbox, getting collaborator access to the store, closing the job and collecting reviews.
Illustrated guide: lulu.us.com/help/guide-onboarding-packages-and-leads
Before you startThis guide continues where "Become an onboarding partner — and how the platform approves you" ends: your partner account is approved and your onboarding profile is published in the directory at partners.lulu.us.com/experts. Steps marked "Partner:" happen in the partner portal at partners.lulu.us.com; steps marked "Merchant:" happen on the public directory or in the merchant's store admin at admin.lulu.us.com. Sending a request is free and commits the merchant to nothing. When on-platform buying is switched on for the merchant's store, they can pay for a fixed-price package or a custom offer you send through Lulu: the payment is held until they accept your delivery, and the platform keeps its commission (see "Sell packages, deliver on time, get paid"). A request gives a partner no access to the store until the merchant grants it. The screenshots use the demonstration partner "Demo Onboarding Studio" and a demonstration merchant.
1. Partner: Add a package
Open "Packages" in the partner portal and click "Add package". Enter a "Title" (3–80 characters) and a "One-line summary", choose the "Service" it belongs to, then set the "Pricing": "Fixed price", "Starting at" (shown as "From …") or "On request" (the card shows "Price on request" and the merchant sends a brief). Enter the "Price" in whole currency units and pick the "Currency"; the line under the fields shows exactly how the price will appear.
- You can have up to 12 active packages.
- The cheapest active package with a price becomes the "From" price on your directory card.
- A package has a minimum price, shown as helper text under the price field. For a free consultation use the "On request" price type.
2. Partner: Say what is included, how long it takes and what is not
Set the "Delivery time" in working days (1–180) and the number of "Revisions included" (0–20); both are optional. Under "What's included" click "Add line" for each deliverable (up to 12 lines), and use "Not included" to set limits clearly — for example product photography or data clean-up above a certain size. Add a "Full description" if you need more detail, then click "Add package".
- Clear limits prevent disputes: say how many products, pages or revisions a price covers.
3. Partner: Order, edit and archive packages
Packages appear on your public page in the order of this list. Drag a package by its handle or use the up and down arrows to move it. Click "Edit" to change a package (changes are live at once and do not need a new review), "Archive" to take it off your page, and "Restore" to bring an archived package back. A package that merchants have already requested is kept as archived so their request still shows it; otherwise archiving removes it.
4. Merchant: Find onboarding partners in the public directory
Anyone can browse partners.lulu.us.com/experts ("Hire someone to set your store up"). Each card shows the partner's logo, tagline, badges (such as the Lulu team or Featured), rating, starting price, where they are based and their main services. Click a card to open the partner's page.
5. Merchant: Filter by service, budget, country and language
Use the search box (name, tagline or city) and the filters "All services", "Any budget", "Anywhere" and "Any language", then click "Search"; "Clear" removes the filters. The budget filter shows partners with at least one package at or below the top of the budget you choose. Budget bands on Lulu: Under LKR 10,000; LKR 10,000 – 25,000; LKR 25,000 – 50,000; LKR 50,000 – 100,000; Over LKR 100,000; Not sure yet.
- Filters are kept in the page address, so a merchant can bookmark or share a shortlist.
6. Merchant: Compare a partner's packages
On a partner's page, the "Packages" section shows each package with its price, what is included (tick marks) and what is not (dashes). The cheapest package is highlighted. Each package has one button: "Buy this package" when it has a fixed price and can be bought online, otherwise "Ask for a quote", which pre-selects that package in the request form. "Request a quote" at the top of the page is for general advice.
7. Merchant: Send a request from the partner's page
Fill in the "Request a quote" form: "Your name", "Email", optional "Store name", "Phone or WhatsApp" and "Existing website", the "Package" (or "No specific package — I need advice"), "What do you need?", "Budget", "When?" and "What do you want built?" (up to 2,000 characters). Click "Send request". Your name, email and message go to that partner only; sending a request commits you to nothing and gives them no access to your store.
- Say what you sell, what is already set up and when you want to go live — it gets you a faster, more accurate quote.
8. Merchant: Request sent
The form confirms "Request sent". A request from the public directory is not linked to a store, so it has no in-app conversation: the partner replies straight to the email you gave, usually within their stated response time. (Requests sent from your store admin — next steps — get an in-app "Messages & offers" conversation as well.) You also receive a copy by email ("We sent your request to <partner>"), and the partner receives "New request from <your name>". Click "Send another request" to contact the same partner again.
9. Merchant: Or hire a partner from your store admin
Store owners can do the same without leaving the admin: open "Onboarding partners" in the left menu ("Hire an expert to set up your store"). Before a store goes live, Home also shows the card "Set up your store yourself, or hire an onboarding partner?" with "Choose a partner" and "Set up myself". The in-admin directory has the same search and filters; click a partner to open their page.
10. Merchant: Send the request from the admin
On the partner's page in the admin, click "Buy this package" to pay for a fixed-price package, or "Ask for a quote" (or "Request a quote" at the top) to send a request. The request form says "Sending as <your name> (<your email>) for <your store>", so you only choose the package, service, budget and timeline, add a phone number if you like, describe the job and click "Send request". A request sent from the admin is linked to your store, which lets you grant access and leave a review later.
11. Merchant: Follow your requests
"Onboarding partners" → "My requests" lists every request your store has sent, with the package, the date and the status: Sent, Partner replied, Quoted, Working together or Closed. "Partner replied" appears as soon as the partner writes to you in the conversation, "Quoted" when they send an offer, "Working together" once you grant them store access or pay for an order, and "Access removed" if you later remove the access of a partner you never paid an order to on that request. Click "Messages & offers" to read and answer the partner in the admin (you also get an email when they write). From here you can also "Grant store access", "Remove access" and "Leave a review".
12. Partner: Open your leads inbox
Every request arrives in "Leads" in the partner portal, and a badge on the menu counts new ones. The table shows the merchant, what they need and when, the budget, the status and when it was received. Use the filters All, New, Contacted, Quoted, Won, Lost and Spam. A new request is also emailed to your profile's contact email.
13. Partner: Read the request and the merchant's contact details
Click a lead to open it. You see the merchant's "Email", "Phone", "Store" and "Website" (whatever they filled in), the "Package", "Service", "Budget", "Timeline", when and where it was received (the partner directory or the store admin) and their "Message". These details are shared with you only because the merchant sent you the request: use them only to answer it.
14. Partner: Reply, set the status and keep private notes
For a request sent from a store admin, answer in the request's "Messages and offers" conversation (or click "Open full conversation" to use Messages): the merchant reads it in their admin and is emailed that you wrote, and it is where you send an offer with "Send offer". Your first message moves the request from New to Contacted and records your "First reply" automatically. A request from the public directory has no store and no conversation — use "Reply by email", which opens your own email program addressed to the merchant. You can still set the "Status" yourself — New, Contacted, Quoted, Won, Lost or Spam — and write a "Private note" (the merchant never sees it), then click "Save". Answering quickly is the strongest signal on your public page.
- The merchant sees your status as: Contacted → "Partner replied", Quoted → "Quoted", Won → "Working together", Lost or Spam → "Closed".
- Some changes happen on their own: sending an offer sets Quoted, the merchant paying for an order or granting you store access sets Won.
15. Partner: Ask for collaborator access to the store
For a request sent from a store admin, the lead has a "Store access" section. Ask the merchant for the 4-digit "Collaborator request code" they find in their admin under Settings → Users → Collaborators, enter it with an optional message and click "Request access". The lead then shows "Access requested — waiting for the merchant to approve it". The merchant can also grant access directly from "My requests" without a code.
- After 5 wrong codes for a store, new requests to that store are locked for 60 minutes and the store is told by email. Ask the merchant for the current code and try again after the hour.
16. Merchant: Grant the partner access to your store
In "My requests" click "Grant store access". The dialog explains that the partner becomes a collaborator: they sign in with their own partner account — never your password — and can work on themes, products, orders, apps, shipping and store settings. They cannot manage users, change your Lulu package, approve paid app charges, see your finances or use Point of Sale, and they do not use one of your staff seats. Click "Grant access". Everything they do is recorded against their own name.
- Granting access needs the permissions to manage users and the store's package — usually the store owner.
- You can remove the access at any time under Settings → Users.
- Default access does not include exporting customers, exporting orders or exporting a store backup. The merchant can turn these on for one partner under Settings → Users → Collaborators → "Edit access".
- Access that is not used for 90 days is removed automatically. The partner gets a warning email after 75 days.
17. Partner: Do the onboarding work
Stores that granted you access appear on your Dashboard under "Client stores"; click "Open admin" (also in the lead) to work in the standard store admin with your own login. Use "Stores" → "Create store" to prepare a theme or demo safely before touching the merchant's store: a "Dev store" to build and test (up to 250), or a "Client transfer store" to build a whole store and transfer it to the client. When the work is done, walk the merchant through their store and let them remove your access under Settings → Users when they no longer need you.
- Never ask a merchant for their password: collaborator access is the safe way in and it stays theirs to revoke.
18. Partner: Close the lead
When the merchant accepts and the job is under way or finished, open the lead, set the "Status" to "Won" (it is already Won if the merchant granted you access or paid an order), update your note and click "Save". Use "Lost" when the merchant chose someone else or did not go ahead, and "Spam" for junk. Closing a lead does not remove any store access — that stays with the merchant.
19. Merchant: Leave a review
A store that has sent a request to a partner from its admin can review them once. In "My requests" click "Leave a review", choose a rating from 1 to 5 stars, add an optional "Headline", describe "What was it like to work with them?" (at least 20 characters) and click "Publish review". Your store name is shown with the review; your email never is. The review updates the partner's rating in the directory straight away.
20. Partner: Reply to reviews
Open "Reviews" in the partner portal. "Merchant reviews of your onboarding work" lists every review with your average rating. Click "Reply", write your public answer and click "Post reply". Each review can be answered once, and the reply cannot be edited afterwards, so keep it factual and polite.
21. Merchant: See reviews on the partner's page
Published reviews appear on the partner's public page under "Reviews from merchants", with the star rating, the store name, the date and the partner's reply. The average rating and number of reviews are shown on the partner's card in the directory.
22. Partner: Pause new work or unlist your profile
If you are fully booked, set "Taking on new clients" to "Not right now" on your Onboarding profile: your page stays live but shows "Not taking new clients". To disappear from the directory completely, click "Unlist"; the status becomes "Unlisted" and nothing is lost — packages, work, leads and reviews stay. Click "Submit for review" when you want to be listed again. Archive packages you no longer offer.
Completion checklist
- At least one active package with a clear price, delivery time and what is and is not included.
- Your packages appear on partners.lulu.us.com/experts/your-address in the order you want.
- New requests show in Leads and arrive at your contact email; you move each one off New quickly.
- For each client, you work through collaborator access — never with the merchant's password.
- Finished jobs are marked Won, and the merchant has removed or kept your access deliberately.
Troubleshooting
Partner: "Add package" is disabled.
You already have 12 active packages. Archive one you no longer offer, then add the new one.
Partner: I am not receiving any requests.
Check that your onboarding profile is Published (not In review or Unlisted), that "Taking on new clients" is set to "Yes", and that the contact email under "How merchants reach you" is correct. Also check your spam folder for "New request from …".
Partner: the lead has no "Store access" section.
Store access can only be requested from leads that were sent from a store admin, because only those are linked to a store. Ask the merchant to grant access from Onboarding partners → My requests after sending the request from their admin, or to approve a collaborator request in Settings → Users → Collaborators.
Merchant: "Grant store access" gives a permission error.
Granting access requires permission to manage users and the store's package, and you cannot hand over more than you have yourself. Ask the store owner to grant it.
Merchant: I can't find "Leave a review".
Reviews are only possible for a partner your store sent a request to from the admin, and each store can review a partner once. If you already reviewed them, the request shows "Reviewed".
Merchant: the request form says "Too many requests. Try again in a minute".
The form accepts a few requests per minute to prevent spam. Wait a minute and click "Send request" again; your answers are still in the form.
Hire an onboarding partner and pay safely
For store owners and staff who manage the plan: choose an onboarding partner, message them, approve an offer, pay through the platform, and follow the order through delivery, revisions and acceptance — with your money held safely until you accept the work.
Illustrated guide: lulu.us.com/help/guide-merchant-hire-partner
Before you startYou need the "Manage plan and billing" permission on your staff account to send messages that involve money, approve or decline offers, and buy a package. Any staff member can read the conversation and view offers. Onboarding partners are optional — you can always set up your own store instead.
1. Choose how you want to set up your store
The first time you open your admin home after your store's sign-up payment settles, a window asks "Set up your store yourself, or hire an onboarding partner?". Click "Choose a partner" to go straight to the onboarding partner directory, or "I'll do it myself" to close it and set things up on your own. Whichever you pick is remembered — the window only appears once. Closing it with Esc or the X asks again next time you open the home page.
- This choice has no effect on your billing or your store's features. You can still browse and hire a partner later from Home or from the partner's own page.
- Only staff with "Manage plan and billing" see this window.
2. Browse partners and their packages
On a partner's page you'll see their rating, response time, and packages. A package with a fixed price shows a "Buy this package" button when on-platform buying is turned on for your store; otherwise you'll see "Request a quote" further down the page. If you'd rather agree on scope and price directly with the partner first, message them instead — they can send you a custom offer.
- "View your order" appears instead of "Buy this package" if you already have an order open for that package.
- A grey note under a package (for example "Buying on-platform isn't turned on for this store yet") explains why buying isn't available right now.
3. Message a partner
Click "Message" on a partner's page, or open Onboarding partners → Messages (or "Messages & offers" on a request under My requests), to start a conversation. The partner answers in the same conversation and you are emailed when they write — you don't need to wait for an email reply. Anyone on your team can read the conversation; only staff with "Manage plan and billing" can send messages, accept or decline offers, or pay. Attachments are links only (up to 5 per message) — there's no file upload. Every order event also appears here as part of the same activity feed, so this is where you'll see updates even after you've bought something.
- Never pay a partner directly through a link, bank transfer or wallet mentioned in a message. Payments made outside the platform have no escrow or refund protection — you'll see this warning if a message looks like it's asking for one.
4. Receive and approve an offer
A partner can send you a custom offer instead of (or in addition to) a fixed package: a price (sometimes discounted from a package's price), a delivery time in days, and a number of included revisions. The offer appears in your conversation with the partner. Review the price, discount, delivery time and revisions before accepting — an offer expires after the date shown, though one you're actively paying for stays valid until that payment finishes.
- "Decline" tells the partner you're passing, with an optional reason. They can send you a new offer any time.
- If the price is $0, accepting only records the agreement — you'd then pay the partner directly, with no escrow protection.
5. Pay for the package or offer
Click "Buy this package" or "Accept and pay" and confirm in the window that opens. Read the note there: your payment is held by the platform until you accept the delivered work — if something goes wrong before then, you can ask for a revision, dispute it, or cancel for a refund while it's late. Confirm to open the payment page. If the payment window doesn't finish (you closed it, or it's still processing), go back to the order — it shows a "Continue payment" button until the payment resolves.
- The confirmation also repeats the platform's rule: pay and get paid only through the platform. Never send money to a partner outside it.
- "Check payment status" on the order page re-checks a payment that seems stuck.
6. Follow the order page
Once paid, the order page shows a live countdown to the delivery date (it turns into "LATE" after the deadline, and "Very late" a day after that), an activity feed combining every order event with your conversation, and an action bar on the side with the buttons available to you right now. The delivery clock starts as soon as you pay — send the partner your brief and any access they need (for example, a collaborator login) right away so they can get started.
- If the order needs your input, the partner will ask for it in the conversation — the clock keeps running while you sort that out.
- Give the partner access with "Grant store access" under Onboarding partners → My requests. Never share your own password.
- A partner starts with default access: no customer export, no order export, no store backup export and no finance. You choose what else they may do under Settings → Users → Collaborators → "Edit access".
- Settings → Activity shows what the partner changed in your admin. Only the store owner can open it.
7. Request a revision if the delivery isn't right
After the partner delivers, "Request revision (n left)" is available if your offer or package included revisions and you haven't used them all. Explain what needs to change; the partner delivers again and your review window opens fresh. Once all revisions are used, the button disappears and you can only accept or dispute what was delivered.
- A revision has no separate deadline of its own — the partner works from your note until they deliver again.
8. Approve or decline a deadline extension
A partner can ask for one extension per order, once. You'll see a banner on the order page with the new date they're proposing and their reason. "Approve new date" moves the delivery deadline (a late order stops being late if the new date is still ahead); "Decline extension" keeps the original date and the partner can't ask again for this order. The original deadline keeps counting down while you decide.
9. Accept, dispute, or cancel
Once you're happy with the delivery, click "Accept delivery" — this releases the payment to the partner (minus the platform's commission). If you don't act, the order accepts itself automatically 7 days after the partner's delivery notice, so it never stays stuck. If something is genuinely wrong and a revision won't fix it, click "Dispute" and explain — a platform administrator reviews it and decides, not the partner. If the partner hasn't delivered and it's more than 24 hours past the due date, "Cancel and get a full refund" becomes the main option; you can also cancel any time before delivery for a full refund of what's left to refund.
- A dispute pauses the auto-accept clock while it's reviewed.
- Canceling before delivery, or once an order is very late, refunds you in full — the partner is told why.
Completion checklist
- The order page shows "Paid" and a delivery countdown right after you pay.
- You can see the partner's delivery note and any links they shared once they mark it delivered.
- A requested revision shows in the activity feed and the partner is notified.
- Accepting the delivery moves the order to a completed status and stops the countdown.
- A canceled or fully refunded order shows the refund in the Refunds list on the order page.
Troubleshooting
I don't see "Buy this package", only "Request a quote".
On-platform buying isn't turned on for your store yet, or the package's price isn't fixed. Ask support to enable it, or request a quote and arrange payment off-platform with the partner (no escrow protection in that case).
The payment page closed before I finished.
Go back to the order — it shows "Continue payment" as long as the payment session is still open, or "Check payment status" to re-check one that might already have gone through. Nothing was charged if the payment never completed.
The offer I wanted to accept says it expired.
Ask the partner to send it again with "Send again" on their side — it becomes a new offer with a fresh expiry date. An offer you were actively paying for stays valid past its expiry until that payment finishes.
"Request revision" isn't there any more.
You've used all the revisions included with your package or offer (the order page shows "None included" or "0 of N left"). At that point you can accept the delivery or dispute it if something is genuinely wrong.
A partner asked me to pay them directly, outside the platform.
Don't. Payments made outside the platform aren't covered by escrow, refunds or dispute resolution. Keep the conversation and payment on-platform, and let support know if this keeps happening.
Sell packages, deliver on time, get paid
For onboarding partners: send offers to merchants, deliver on time, handle revisions and extensions, and track what you've earned — including how and when the platform pays you by bank transfer.
Illustrated guide: lulu.us.com/help/guide-partner-orders-earnings
Before you startYou need an active partner account. Bank details for payouts are stored encrypted and require your current password to change. Money only moves for live (non-test) orders — a test order (paid with a test or sandbox card) is flagged and never counted in your earnings or paid out.
1. Send an offer
From a conversation with a merchant, click "Send an offer". Base it on one of your active packages (you can only discount its price, as an amount or a percentage) or choose "Custom offer" to set your own price and currency. Set the delivery time (1–90 days), the number of included revisions (0–10), and how long the offer stays open (1–30 days). "Save draft" keeps it private to you; "Send offer" puts it in front of the merchant. Sending a new offer automatically supersedes any other offer you'd sent this merchant for the same request.
- The delivery clock starts when the merchant pays, not when you send the offer.
- The platform sets a minimum offer price — you'll see a validation message if you go below it.
- You can keep up to 5 drafts per conversation.
2. Deliver the work
Once an order is paid, work from the merchant's brief in the conversation. When you're done, open the order and use the delivery form: write a note describing what you delivered, and add up to 5 links. Click "Mark delivered" (or "Deliver revision" if this follows a revision request). The merchant is notified and their review window opens — if they don't act, the order accepts itself automatically after 7 days.
- If you deliver after the due date, the order still records it as "Delivered late", but delivering is always possible.
3. Ask for more time if you need it
You can request one extension per order. On the order's action bar, click "Request extension", propose a new delivery date and explain why. The merchant decides — the original due date keeps counting down (and can still go late) until they approve or decline. You can't ask for a second extension on the same order.
4. Handle a revision request
If the merchant asks for a revision, the order moves to "In revision" and their note appears at the top of the order page. Make the change and deliver again the same way as your first delivery — the revision count on the order goes down by one each time. Once all revisions are used, the merchant can only accept the delivery or dispute it; they can no longer request another revision.
5. Check your earnings
Open Partners → Earnings for a breakdown by currency: what's Held (delivered but not yet accepted), Due to you (accepted and waiting for a payout), what's already In an open payout, and what's been Paid out to date. If you owe the platform money — for example a clawback from a refund after you were already paid — it shows as Outstanding debt, which the next payout automatically deducts.
- Test orders are listed separately, with no totals — they're never paid out.
- Commission is taken from the price the merchant actually pays, after any refund, and is fixed at the rate in effect when the order was approved — it never changes on an existing order even if the platform's rate changes later.
6. Add your payout bank details
On the Earnings page, click "Add bank details" (or "Change details" if you've already added them). Enter your bank name, account holder name, account number, and optionally the branch and SWIFT/BIC code, plus your country. Confirm with your current password — this is required every time these details change, and you'll get an email confirming the change. Your details are stored encrypted; nobody can see them again except the platform administrator actively transferring you a payout, and only for as long as that transfer is in progress.
- If you see "Bank details can't be saved right now", the platform hasn't finished setting up secure storage for them yet — contact support.
7. How and when you're paid
The platform doesn't pay you automatically the moment an order is accepted — a platform administrator prepares a payout covering everything you're due in one currency, approves it, and then sends the bank transfer themselves, recording the reference once it's done. This can take a little while, especially for your first payout. You'll see the amount move from "Due to you" to "In an open payout", then to "Paid out" once the transfer is recorded.
- A payout nets out any open clawbacks or advances against what's due, so what actually gets transferred can be less than your raw "Due to you" total.
8. Advances and clawbacks, in plain words
A clawback happens when a merchant is refunded for an order after you'd already been paid for it — the amount is taken from your next payout rather than asked back directly. An advance is money the platform already sent you outside a normal payout (for example, evidence of a bank transfer that arrived after a payout was canceled) — it's netted the same way against what you're due next. Either can be waived by a platform administrator, which means the platform absorbs it and you keep the money; you'll see this reflected as your debt going away.
9. Never take payment off-platform
Always send offers and get paid through the platform. Don't ask a merchant for bank details, a payment link, or to pay you directly — messages that look like they're steering payment off-platform show a warning, and off-platform payments have no escrow, refund or dispute protection for either side.
Completion checklist
- A sent offer appears in the merchant's conversation with delivery days, revisions and price.
- Marking an order delivered notifies the merchant and starts their review window.
- The Earnings page shows the order's amount under Held right after you deliver, then Due to you once accepted.
- Payout bank details are saved and show under Payout bank details with a "Last changed" date.
- A paid-out order shows a payout date on its order page under Price and payout.
Troubleshooting
I can't send an offer below a certain price.
The platform sets a minimum offer price (shown in the validation message). Raise your price to at least that amount, or ask the merchant to consider a different package.
My extension request is still pending after a long time.
Extensions are decided by the merchant, not automatically. The order's original due date keeps running (and can go late) until they approve or decline — message them if it's urgent.
An order shows in Test orders and isn't counted anywhere else.
That order was paid with a test or sandbox card. Test orders run through the same order page but never generate real earnings or a real payout.
I can't save my payout bank details.
Check that you entered your current account password correctly. If the page says bank details can't be saved right now, the platform's secure storage for them isn't set up yet — contact support.
My earnings show a debt I don't understand.
It's most likely a clawback from a refund on an order you were already paid for, or an advance recorded against you. Check the order's Price and payout section, or ask support to explain a specific entry.
Follow one onboarding job from both sides
One onboarding job from start to finish, seen from the merchant's store admin and from the partner portal: getting listed, the request, in-app messages, a custom offer and payment, store access, delivery, review, hand-over of a client transfer store and customer registration.
Illustrated guide: lulu.us.com/help/guide-partner-merchant-onboarding-job
Before you startSteps marked "Merchant:" happen in the store admin at admin.lulu.us.com; steps marked "Partner:" happen in the partner portal at partners.lulu.us.com/partners. The partner needs an approved partner account and a Published onboarding profile with at least one active package — a Draft or In review profile is not in the directory, so nobody can find it, message it, request a quote or buy from it, and it receives no requests. On the merchant side any staff member can read requests and conversations; sending messages, accepting offers and paying need the "Manage plan and billing" permission, and granting store access also needs "Manage users" (usually the store owner). Requests are free and commit the merchant to nothing. All conversations and payments stay on the platform.
1. Partner: Get listed in the directory
Open "Onboarding profile" (under More). The status box lists what is still missing; every item is required before you can submit: a business name, a one-line tagline (at least 10 characters), an About text of at least 80 characters, at least one service, at least one active package, a contact email and a logo. Click "Save", then "Submit for review". The status becomes "In review" and the platform team either publishes the profile or sends it back with a reviewer note — you are emailed either way. There is no fixed turnaround for a profile review.
- A directory listing also needs the directory tier (Plus by default) or an invitation. Below it, the page shows "Request invitation" instead of "Submit for review": finish the checklist, add an optional "Note for the reviewers" and click it — invitation requests are reviewed within 5 business days.
- Until the profile is Published you get no leads, messages or orders. Merchants can still reach you through a store you were already working with.
2. Merchant: Find the partner
In the store admin open "Onboarding partners" in the left menu ("Hire an expert to set up your store"), search or filter, and click a partner. Their page has three buttons at the top: "Message" (start a conversation), "Public page" (the same profile on the public directory) and "Request a quote". Under "Packages" each package shows one button: "Buy this package" for a fixed price you can pay online, "View your order" if you already have an open order for it, otherwise "Ask for a quote".
- "Buy this package" appears only when on-platform buying is switched on for the store and you have "Manage plan and billing".
3. Merchant: Send the request
Click "Request a quote" (or "Ask for a quote" on a package). The form says "Sending as <your name> (<your email>) for <your store>"; choose the package, service, budget and timeline, describe the job and click "Send request". The request appears under Onboarding partners → "My requests" (the page is titled "My partner requests") with the status "Sent", and you get an email confirming it went out.
4. Partner: Open the request in Leads
The request arrives in "Leads" (the menu badge counts new ones) and at your profile's contact email. Click it to see the merchant's contact details, store, package, budget, timeline and message. A request sent from a store admin also shows a "Store access" section and the "Messages and offers" conversation.
5. Partner: Answer in Messages and offers
Write your answer in the request's "Messages and offers" conversation, or click "Open full conversation" to continue under "Messages". The merchant reads it in their admin and is emailed that you wrote (at most one email per conversation every 15 minutes). Your first message moves the request from New to Contacted and records your "First reply" — the merchant's status changes to "Partner replied". You can also set the "Status" and a "Private note" yourself and click "Save".
- "Reply by email" opens your own email program. Use it for requests from the public directory: they are not linked to a store and have no in-app conversation.
- Links only — there is no file upload. A message that looks like a request to pay outside the platform shows a warning; payments outside the platform have no escrow, refund or dispute protection.
6. Merchant: Reply and follow the status
In "My requests" click "Messages & offers" on the request (or open Onboarding partners → "Messages"). The status column reads: Sent (the partner has not answered yet), Partner replied, Quoted (the partner sent an offer), Working together (you granted access or paid an order), Access removed (you granted access and later removed it, with no paid order on this request) or Closed (the partner closed the request as lost or spam).
7. Partner: Send a custom offer
In the conversation click "Send offer". In "Send an offer" either base it on one of your active packages (you can only lower its price) or choose "Custom offer (no package)" and set your own price and currency. Set "Delivery (days)" (1–90), "Revisions" (0–10) and how long the offer stays open (1–30 days, 14 by default), then click "Send offer" (or "Save draft"). The request moves to Quoted. A new offer for the same request replaces your previous one unless the merchant is already paying for it.
- You cannot send an offer to your own partner stores.
- Prices below the platform's minimum offer price are refused with a message.
8. Merchant: Accept and pay — or decline
The offer appears as a card in the conversation with the price, any discount, delivery days and revisions. Click "Accept and pay <price>" and complete the payment page — the platform holds the money until you accept the delivered work — or "Decline" (with an optional reason). An offer with a price of 0 shows "Accept offer": it only records the agreement, with no payment and no escrow. Once paid, the order appears under Onboarding partners → "Orders" for you and under "Orders" in the partner portal, and the request becomes Working together. The delivery clock starts when you pay.
9. Merchant: Grant store access
In "My requests" click "Grant store access". The dialog explains what the partner can do: they sign in with their own partner account and can work on themes, products, orders, apps, shipping and store settings, but cannot manage users, change your plan, approve paid app charges, see your finances or use Point of Sale, and they don't use a staff seat. Click "Grant access". The row shows "Access granted" and "Remove access", the status becomes Working together, and the partner is emailed.
- The partner starts with default collaborator access. It does not include exporting customers, exporting orders, exporting a store backup, finance or approving paid app charges. To change what this partner can do, open Settings → Users → Collaborators, find them under "Collaborator access" and click "Edit access". Tick or untick sections, then click "Save access". This works on every plan.
- Granting needs both "Manage users" and "Manage plan and billing", and you can only hand over permissions you hold yourself.
- A collaborator can never manage users or roles, change your plan, transfer or close the store, use Point of Sale or restore a backup.
10. Partner: Or ask for access with the 4-digit code
If the merchant prefers, ask them for the "Collaborator request code" shown under Settings → Users → Collaborators. In the lead's "Store access" section enter it, add an optional "Message" and click "Request access". The lead shows "Access requested — waiting for the merchant to approve it in Settings → Users → Collaborators"; the merchant is emailed and approves it under "Requests".
- A wrong code answers "No store matches that address and code". Codes are tried at most 10 times a minute, and the merchant can replace the code with "Generate new code" at any time — ask for the current one.
- Type the code carefully. After 5 wrong codes for a store, new requests to that store are locked for 60 minutes and the store is told by email. Nobody gets access. Wait, then ask the merchant for the current code.
- A wrong code, a wrong store address and a locked store all show the same message: "No store matches that address and code".
11. Partner: Work in the store
Stores that granted you access appear on your Dashboard under "Client stores"; click "Open admin" (also in the lead) to work in the normal store admin with your own login. Everything you do is recorded under your name.
12. Partner: Deliver, ask for more time, or decline
Open the order under "Orders". The "What's next" box offers "Deliver now" (write a delivery note and add up to 5 links, then "Mark delivered"), "Request extension" and "Decline order". You can ask for one extension per order, before you deliver, to a date at most 30 days after the current due date; the merchant approves or declines it and the original date keeps running meanwhile. "Decline order" (a reason of at least 10 characters) is only possible before you deliver and refunds the merchant in full.
- When the merchant asks for a revision the order shows "The merchant asked for a revision"; make the change and click "Deliver revision".
- Disputes are opened by the merchant and decided by the platform team, not by either side. Partners cannot issue a partial refund themselves — answer in the conversation and the platform team resolves it.
13. Merchant: Accept the delivery
On the order page click "Accept delivery" to release the payment to the partner. While revisions remain you can click "Request revision (n left)" instead; if something is genuinely wrong, click "Dispute". If you do nothing, the order accepts itself 7 days after the delivery notice. Before delivery you can "Cancel order" for a refund, and once the order is more than 24 hours late "Cancel and get a full refund" leads.
14. Partner: Follow orders and earnings
"Orders" lists your orders with a status filter ("All statuses", "Open", …). Tick "Include test orders" to also show orders paid while the platform's payments ran in test mode; a test order never counts toward earnings and is never paid out. "Earnings" shows, per currency, what is Held (delivered, not yet accepted), Due to you (accepted), In an open payout and Paid out.
- The platform's commission (10 % unless the platform sets another rate) comes off the price the merchant paid and is fixed on each order when it is bought.
- A package priced in LKR is paid and paid out in LKR; one priced in USD in USD. Payouts are prepared and transferred by the platform team, one currency at a time.
15. Merchant: Leave a review — Partner: reply once
As soon as the store has a request or an order with the partner, "Leave a review" is available in "My requests" — it does not wait for the work to finish. Choose 1–5 stars, an optional "Headline" and at least 20 characters under "What was it like to work with them?", then click "Publish review". It is published straight away; each store reviews a partner once. The partner answers from "Reviews" in the portal with "Reply": one public reply per review, which cannot be edited afterwards.
16. Merchant: Remove access when the work is done
Access does not end when an order is accepted or when the partner closes the request. It ends on its own only when the partner has not signed in to your store for 90 days; they get a warning email after 75 days, and you get an email when it expires. When you no longer need the partner, remove the access yourself: click "Remove access" in "My requests", or under Settings → Users → Collaborators open their row menu and choose "Remove collaborator". They are signed out of the store straight away, and a request that was only won through store access then shows "Access removed".
- Partners: open the store admin from your Dashboard before the date in the warning email to keep your access. If it expired, ask the store owner to give it back under Settings → Users → Collaborators.
- The Collaborators tab shows "Access ends <date> if not used" next to a collaborator.
- Store owners: Settings → Activity lists what each collaborator changed in your admin.
17. Partner: Build on a client transfer store and transfer it
To build a new store for a client, go to Dashboard → "Stores" → "Create store", choose "Client transfer store", type a store name and click "Create". It has Advanced plan features; tick "Enable Plus features" if your client needs Plus. When it is ready, click "Transfer to client", enter the "Client's email" and an optional "Personal message" (up to 500 characters) tick "The domain and the payment gateway accounts used by this store belong to my client, not to me." and click "Send transfer". The client gets an email with an accept link valid for 30 days; "Resend invite" sends a fresh one. When the client accepts, they become the store's owner and land on the Plan page to choose a plan; you keep collaborator access until they remove it, and the store moves to your "Client stores".
- The merchant sees: the transfer email with your message, an accept page, then Settings → Plan with a hand-over notice. Nothing changes on the store until they accept.
- "Transfer to client" is offered only on client transfer stores. Dev stores can't be transferred. Every partner store you created before 30 October 2026 is now a client transfer store.
- Until the transfer, the store is always password-protected and takes test orders only: no real payments, gift cards or store credit. It can't go live.
- A paid app plan is free on your partner stores only if it is a free plan, a plan marked "Free for partners", or (on dev stores) a plan of your own app. Other paid plans show "Not free on partner stores" and can't be chosen; the store owner picks them after the transfer.
- After the transfer, apps that were free on your store start the app's normal free trial, then bill the new owner.
- A paid Theme Store theme stays a trial on a partner store: you can customise and preview it, but its code (custom.js and head snippets) is read-only and it can't be published. The client buys it after the transfer.
- "Send transfer" stays greyed out until you tick the confirmation. Your confirmation is stored with the transfer.
- If a custom domain or a live payment gateway is connected, the drawer warns you and names it. After the transfer the store keeps using them, so make sure your client controls the domain's registration and DNS and that the gateway account is their own.
- If the client does not accept within 30 days, the invitation expires and we email you. Send a new one with "Transfer to client".
18. Partner: Register a customer you are launching
Under "Customers", fill in "Register a customer": "Program", "Merchant legal name", an optional business registration number, "Merchant contact email", the store domain if known, the "Intended plan" and "Merchant consent" — where the merchant agreed that you launch their store (for example "signed proposal #42" or "email of 3 Oct from the owner"). Keep the original: the platform may ask for it. Click "Register customer". The answer is always "Registered — under review. The registration holds for 90 days."
- Under review means the platform team checks the claim; you see it become Qualified, Converted (a store enrollment of this customer was confirmed), Rejected or Expired (90 days passed without one).
- Registering requires an approved Partner or Reseller Program membership with the current agreement accepted.
Completion checklist
- The partner's onboarding profile shows Published and the partner appears under Onboarding partners in the merchant admin.
- A request sent from the admin shows in the partner's Leads and in the merchant's My requests as Sent.
- The partner's first message in Messages and offers turns the merchant's status into Partner replied.
- A sent offer shows as Quoted; paying it creates an order on both sides.
- After Grant access the row shows Access granted and Working together, and the store is under the partner's Client stores.
- Access is removed deliberately when the work is done.
Troubleshooting
Partner: my profile is a Draft and I get no requests.
Draft and In review profiles are not in the directory, so merchants cannot message, request a quote or buy from them. Finish the checklist and click "Submit for review" — or "Request invitation" if your tier is below the directory minimum — and wait for the profile to be published.
Merchant: My partner requests says "Sent" although the partner answered.
The status follows the conversation: it changes to "Partner replied" as soon as the partner writes in Messages & offers, and to "Working together" once you grant access or pay an order. If the partner answered only by email outside the platform, the status stays "Sent" until they write in the conversation or update the request.
Merchant: the partner says they will reply from their own email.
That only applies to requests sent from the public directory, which are not linked to a store. Requests sent from your admin have an in-app conversation: ask the partner to answer under Messages & offers so the conversation and any offer stay on the platform.
Partner: "Include test orders" shows nothing.
Test orders exist only when the platform's payment gateway runs in test mode at the moment of purchase. Orders paid with live payments are real orders, listed without the tick.
Partner: I can't send an offer or the merchant can't buy.
You cannot sell to your own dev stores or client transfer stores, the profile must be Published and your account active, and on-platform buying must be switched on for the merchant's store.
Partner: the lead has no "Store access" section.
Only requests sent from a store admin are linked to a store. Ask the merchant to send the request from their admin, or to grant access from My partner requests.
Resell prepaid plans to your clients
For partners: check whether you can join the Reseller Program, apply, hand a store over with "Bill this store through my reseller account", pay the client's prepaid plan term at a discount, renew it each year, tell us when you will not renew, and know what happens, day by day, if a renewal isn't paid.
Illustrated guide: lulu.us.com/help/guide-reseller-program-live
Before you startYou need an approved partner account. To apply you need at least 10 active attributed stores, unless our team invites you. As a Reseller Partner you prepay a client store's plan for a fixed term (currently 12 months) at a discount (currently 20%) off the plan's yearly list price, and you bill your client yourself, in your own way. The client owns the store and its data. Apps, themes and other extras are always billed to the client directly.
1. Check whether you can apply
In the partner portal, open More → Reseller. "Your reseller status" shows where you stand, and "Active attributed stores" shows your count against the minimum, for example "4 / 10 needed". While you are below the minimum the status reads "Not eligible yet" and "Apply to resell" is greyed out, with the reason and your count underneath. Memberships and agreements (More → Application) uses the same check, so "Apply for the Reseller Program" is greyed out there too, with the same reason.
- A store counts when it is attributed to you (you handed it over or referred it), is live on an active paid plan, isn't frozen, isn't a dev store or a client transfer store you still own, and has a plan payment from the last 90 days or a prepaid plan period that covers today.
- Stores you resell count too, while their prepaid term is paid and running.
- Stores where you are the owner or an admin yourself, and test payments, never count.
- If you drop below the minimum after you are approved, you stay a Reseller Partner.
2. Apply to resell
Once you reach the minimum, your status changes to "Eligible — apply". Click "Apply to resell" on the Reseller page. Your status changes to "Application pending" and our team reviews it. When you are approved we email you and your status becomes "Active reseller".
- We also check the minimum again when you apply, so the count on the page is what counts.
- Our team can also invite you without an application. An invited partner becomes an Active reseller right away, whatever their store count.
- You can also apply from Memberships and agreements → "Apply for the Reseller Program". You then also add the support contact your clients should use and confirm the reseller training before you submit.
3. Hand a store over with reseller billing
On your Dashboard, under Stores, click "Transfer to client" on the client transfer store. Enter your client's email and, if you like, a personal message. Tick "Bill this store through my reseller account" and choose the plan. Each plan shows what you pay for the term and its yearly list price. Then tick the confirmation "The domain and the payment gateway accounts used by this store belong to my client, not to me." and click "Send transfer".
- "Transfer to client" appears only on client transfer stores, never on dev stores. Every partner store you created before 30 October 2026 is now a client transfer store.
- The tick box appears only while your status is Active reseller. A suspended reseller can't start a new resold hand-over.
- "Plans you can resell" on the Reseller page lists the plans and today's prices. A plan with no yearly list price can't be resold, and the page says why. Plus is priced by quote for each merchant, so it has no yearly list price and can't be resold on a prepaid term. Contact partner support about a Plus client.
- The client's email has a link to accept the store. The link works for 30 days. "Resend invite" sends a new one.
- "Send transfer" stays greyed out until you tick the confirmation. If a custom domain or a live payment gateway is connected to the store, a warning names it above the tick box. Make sure your client controls both before you send.
- While one of your resold stores is overdue you can't tick the reseller box or create stores. See "While a store is overdue" below.
4. Your client accepts the store
Your client opens the link and clicks "Accept ownership". Before they accept they see "Your plan: <plan> for 12 months, paid by <your partner name>" and that apps, themes and anything outside that plan are billed to them directly. When they accept, they become the store's owner. The plan, the discount and the term are locked on that day, so a later price change doesn't change this term.
- The store then appears on the Reseller page under "Resold stores" as "Awaiting payment".
5. Pay for the term
On the Reseller page, under "Resold stores", click "Pay now" next to the store. A secure payment page opens. When the payment is confirmed you return to the Reseller page with "Payment received — the store’s prepaid term is active." The store shows as Active with its term dates, and "Invoice PDF" downloads your invoice.
- The term starts on the day your payment is confirmed and runs for 12 months.
- Pay soon after your client accepts. If you haven't paid within the payment window (currently 14 days), the hand-over is cancelled and your client can choose and pay a plan themselves.
- While the term runs, your client's plan isn't charged to them. Apps, themes and other extras they add are billed to them.
6. Renew before the term ends
We email you 30, 14, 7 and 1 days before the term ends ("Renew <store>'s plan"), with the renewal amount. From 30 days before the end the store shows "Renewal due" and a "Renew" button. Click "Renew" and pay. The next term starts on the day the current one ends.
- A renewal is priced at the plan's yearly list price on the day you renew, less your discount.
- You can renew only while your status is Active reseller. While your reseller account is suspended, renewals are paused.
- You can renew a plan only while it is still on the list of plans you can resell.
- Reminders go to you only. Your client hears nothing while you renew on time.
7. If a renewal isn't paid
Nothing is charged to your client automatically, at any point. The days below count from the day the term ended. The store row on the Reseller page stays "Renewal due" and shows where it stands, for example "Unpaid — renew now."
- Day 0: we email you that the plan is overdue, with every date below. The store keeps working. You can't create stores or start resold hand-overs until it is paid.
- Day 3: your client is told for the first time, by email and on Settings → Plan and Settings → Billing. They are not charged and have nothing to do yet.
- Day 14: your client is offered to pay for the plan themselves, at the list price. If they pay, the store is billed to them from then on and your resold subscription ends. We email you when the offer opens.
- Day 30: the storefront is paused. Visitors see a "temporarily unavailable" page. Your client can still sign in to the admin, export their data and pay for the plan.
- Day 90: the store is closed and the resold subscription ends. The store then shows "Lapsed". Nothing is billed to your client. They keep their data and can reopen the store by choosing a plan.
- You can click "Renew" and pay at any time until the store is closed, unless your client has already paid. The new term starts on the day the old one ended, not on the day you pay. Paying brings a paused storefront back at once.
- The day counts are fixed for a store when it enters its renewal window, 30 days before the term ends. The note under "Resold stores" shows the counts in force.
8. Tell us when you will not renew
If you will not renew a store, click "Don’t renew" on its row under "Resold stores" before the term ends. The row then reads "Not renewing — the owner can pay for the plan themselves from <date>". Changed your mind? Click "Renew after all".
- Your client is told 30 days before the term ends that you will not renew, and that from the term end they can choose a plan and pay for it themselves.
- The term you paid for is never shortened. The store runs to the end of it.
- A store marked this way is not treated as overdue, so it does not block you from creating stores.
- If your client doesn't pay either, the storefront is paused 30 days after the term ended and the store is closed 90 days after it ended.
- If your client takes the plan over, you have nothing more to pay for that store. For resold hand-overs accepted from 20 November 2026 you also earn no partner commission on what the owner pays after the takeover. Earlier hand-overs keep their terms.
9. While a store is overdue, you can't add stores
From the day a resold term ends unpaid, your Reseller page shows "You have an overdue resold store, so you can’t create new stores or start new resold hand-overs. Pay the overdue store below to lift this."
- It applies to every store type on your Dashboard: dev stores, client transfer stores and demo stores.
- An unpaid first term counts too: if your client accepted and you did not pay within the payment window (currently 14 days), the block applies until a plan is paid for that store or the store is closed.
- The block lifts when none of your stores is overdue any more: you paid, the owner took the plan over, or the store was closed.
- Hand-overs where the client pays their own plan are not blocked. Only "Bill this store through my reseller account" is.
10. Know what your client sees
In their store admin, Settings → Plan shows "Billed through <your partner name>", with the plan you prepaid and the date it runs until. They can't change or cancel the plan there; they are asked to contact you. A bigger plan than the one you paid for is billed to them directly, through support. Before you pay, they see that the store is waiting for your payment, and the date after which they can choose a plan themselves. If the term ends unpaid, they see nothing for the first 3 days. Then they see that the plan has not been renewed and the date it was paid until. From day 14 they see "You can now pay for your plan yourself" and the plan picker, with the first month paid and the next month free.
- Your client never sees what you paid. Your payments don't appear among their invoices.
- Your client sees dates only: never your price, your discount or your terms.
- Only the store owner can take the plan over. Their staff see "Only the store owner can do this."
Completion checklist
- The Reseller page shows your status as Active reseller.
- The hand-over drawer shows "Bill this store through my reseller account" and the plans you can resell with your price.
- After your client accepts, the store is under "Resold stores" as "Awaiting payment".
- After you pay, the store shows Active with its term dates, and "Invoice PDF" downloads the invoice.
- Your client's Settings → Plan shows "Billed through" with your name.
- You know the dates: reminders 30, 14, 7 and 1 days before the term ends; owner told on day 3; owner can pay from day 14; storefront paused on day 30; store closed on day 90.
- Stores you will not renew are marked "Don’t renew" before their term ends.
Troubleshooting
"Apply to resell" is greyed out.
The reason is shown under the button. Usually you have fewer than 10 active attributed stores; the page shows your count. It may also be that you have already applied or your reseller account is suspended.
I can't see "Bill this store through my reseller account" on the hand-over.
It appears only while your status on the Reseller page is Active reseller.
A plan says it cannot be resold.
The prepaid term is priced from the plan's yearly list price. Plus is priced by quote for each merchant and has no yearly list price, so it can't be resold. Contact partner support about a Plus client.
"Pay now" is gone and the store shows Cancelled.
The payment window after your client accepted closed before the payment was made, so the hand-over's reseller billing was cancelled. Your client can now choose a plan themselves.
I don't see "Renew" yet.
Renewal opens 30 days before the term ends. We email you when it opens.
My payment didn't complete.
Click "Pay now" or "Renew" again. If you were charged but the store doesn't show Active after a few minutes, contact partner support.
Reseller billing says it isn't available on my account yet.
That's expected. You pay for the stores you resell on the Reseller page, as this guide describes.
I can't create a store, or the reseller tick box is refused.
One of your resold stores is overdue. The message reads "You have an overdue resold store. Pay it on your Reseller page before you create another store." Pay the overdue store on the Reseller page. The block lifts as soon as none of your stores is overdue.
"Send transfer" is greyed out.
Enter the client's email and tick "The domain and the payment gateway accounts used by this store belong to my client, not to me." Both are required.
My client paid for the plan themselves. What happens to my subscription?
It ends. We email you that the store is now billed to its owner. There is nothing more for you to pay for that store.
The store shows Lapsed.
It was closed 90 days after the term ended because nobody paid. The resold subscription has ended and can no longer be renewed. The owner can reopen the store by choosing a plan.
Save a card and pay faster next time
For shoppers: sign in and confirm your email, tick the box to save your card at checkout, pay with a saved card next time, remove a card you no longer want kept, and what to do if your bank's 3D Secure check fails.
Illustrated guide: lulu.us.com/help/guide-saved-cards-shopper
Before you startThis only works at stores that take card payments through Stripe and have turned saving on — not every store offers it, and it never works as a guest. You'll need an account at the store, and your account email needs to be confirmed once before your first saved card.
1. Sign in before you check out
Saving a card is only offered to a signed-in customer. As a guest you can still pay by card, but you won't see any option to save it or to use a card you saved earlier — the payment section just asks for your card details, as shown below. Sign in (or create an account) before you reach the Payment step if you want to save a card this time.
2. Confirm your email
Saving a card also needs your account's email address confirmed. If it isn't yet, your account's Saved cards section shows this exact note: “Confirm your email to use saved cards: sign out, choose “Forgot password” on the sign-in page and set a new password from the emailed link.” Follow it exactly: sign out, go to the sign-in page and choose “Forgot password”, then open the email that arrives and set a new password from its link. That confirms the email is really yours and you're signed back in.
- You only need to do this once. After your email is confirmed, saving and using cards works normally on every order.
- If you never receive the email, check your spam folder before asking the store to resend it.
3. Tick the box to save your card
When you pick Credit card at checkout, signed in with a confirmed email, you'll see an unticked box: “Save this card for future purchases at [store name]”, with a note that the card is kept securely by Stripe, the store's payment provider — never by the store itself — and that you can remove it at any time. Tick it before you place the order. Leave it unticked and nothing is saved, exactly like before.
- The box only appears when the store has saving turned on. If you don't see it, that store hasn't enabled saved cards.
4. Pay with a saved card next time
On your next order at the same store, the Payment step lists your saved cards by brand and last 4 digits, with “Use a new card” as an extra option. Pick a saved card and you skip typing your card number again; pick “Use a new card” to pay with a different card (and tick the save box again if you want to keep that one too).
5. Remove a saved card
Go to your account and open Saved cards. Each card shows its brand, last 4 digits and expiry with a Remove button. Click Remove, then confirm with the Remove button that appears next to “Remove this card?” (or Cancel to keep it). It's gone from your account immediately and can no longer be chosen at checkout.
- Before you've saved any card the same page just says: “No saved cards yet. When you pay by card while signed in, you can tick “Save this card” to check out faster next time.”
6. Why the first few payments ask for 3D Secure
3D Secure is your bank's own check that it's really you paying — usually a one-time code by text or app, or a confirmation in your banking app. Many stores ask for it on your first few payments there and then stop asking unless your bank itself requires it. This isn't something the store chooses about you personally; it's the same for every new customer at that store, and it happens whether or not you're saving a card.
7. If your bank's check fails or doesn't appear
If you cancel or fail the bank's check, the payment simply doesn't go through and nothing is charged — no order is created and no card is saved from that attempt. Try again: reopen your banking app or check for a new code, and make sure you approve the request from the same device or number your bank has on file. If the check never appears at all, wait a moment and try placing the order again; if it keeps failing, contact your bank or try a different card.
8. Open Payment methods in your account
Your account now has its own “Payment methods” page, separate from checkout — go to your account and open it to see every card you've saved at this store, add one, or make changes, any time, not just while you're buying something.
9. Add a card without buying anything
Click “Add a card”. Enter the card details in the store's secure card field, tick “Save this card for future purchases at [store name]”, and enter your account password if you're asked for it (skipped if you've signed in very recently). If your bank asks for a 3D Secure check, complete it the same way you would at checkout. The card is saved once you see “Card saved”.
- A new card can also become your primary card straight away — tick “Make this my primary card” before you save it.
10. Make a card your primary card
Your primary card is the one already picked for you at checkout, though you can still switch to another saved card or “Use a new card” before you pay. On Payment methods, open the card you want to switch to and choose “Make primary”. The card that was primary before simply becomes an ordinary saved card.
11. Edit a card, or add a nickname
Open a saved card and choose “Edit” to change its expiry month or year, the name on the card, its billing address, or give it a nickname (like “Work card”) so it's easier to tell apart. The card number itself can never be edited — if it's changed, add it again as a new card and remove the old one.
12. Remove a card (confirm with your password)
Open the card and choose “Remove”, then confirm. If you haven't signed in within the last 15 minutes, you're asked for your account password first, as an extra check that it's really you. Once removed, that card can't be used at checkout — and if it was your primary card, your most recently added card becomes primary instead.
13. Expired and Expires soon badges
A card shows an “Expired” badge once its expiry date has passed, or “Expires soon” shortly before. An expired card can't be chosen at checkout or made primary — edit it with a new expiry date if you still have the same physical card, or remove it and add the replacement.
14. The 10-card limit
You can save up to 10 cards at a store. Once you're at that limit, “Add a card” is replaced with a note telling you to remove one first — remove a card you no longer use, then add the new one.
15. “This card is already saved”
If you try to add a card that's already in your wallet at this store, nothing new is created — you'll see “This card is already saved” and your existing entry for that card is kept, along with any nickname or primary choice you already had.
16. If saving a card doesn't finish
If your bank approves the card but something interrupts the save (a dropped connection, for example), you don't need to re-enter your card details — you'll see a message asking you to press “Save card” again, and the store finishes confirming that same attempt. If the problem is with the card itself (declined, or the bank's check failed), fix that or try a different card instead.
17. Emails you receive about your saved cards
You get a short security email whenever a card is saved to, or removed from, your account at a store — naming the card's brand and last 4 digits only, never the full number. If you ever get one you don't recognise, sign in, change your password, check your saved cards, and contact the store.
Completion checklist
- You're signed in and your account email is confirmed (no “Confirm your email” note on Saved cards).
- You saw and ticked the “Save this card” box before placing an order you wanted saved.
- Your saved card appears on your next order at that store, with “Use a new card” as the other option.
- You know where to remove a saved card if you no longer want it kept.
Troubleshooting
I'm signed in but there's still no “Save this card” box.
Confirm your email first (Saved cards on your account page tells you if it isn't confirmed yet), and check that this particular store has saved cards turned on — not every store offers it.
A store asked for 3D Secure again even though I've ordered there before.
That's normal and not a mistake: your bank, the card network, or the store's fraud protection can ask for it on any payment, not just your first few, and this is completely separate from anything about saving a card.
I removed a card by mistake.
There's no undo — add it again the normal way, by ticking “Save this card” the next time you pay with it.
The payment failed after the bank's check.
Nothing was charged and no card was saved. Try the order again, approving the bank's check on the device it expects; if it keeps failing, use a different card or contact your bank.
Connect your own domain (and how SSL works)
For store owners who already own a domain: point it at your Lulu store with DNS records (Cloudflare or any other provider), understand why SSL needs no separate step, and set the domain as primary.
Illustrated guide: lulu.us.com/help/guide-connect-existing-domain-ssl
Before you startYou need access to Settings in your store admin, and access to your domain's DNS records at your registrar or DNS provider (GoDaddy, Namecheap, Cloudflare, Google Domains, your IT department, etc.). Every store already has a free address, `<your-handle>.lulu.us.com`, so connecting your own domain is optional. Buying a new domain through Lulu instead needs a payment method on file; transferring one in goes to the platform's ops queue and isn't instant.
1. Open Settings → Domains
In your store admin, go to Settings, then Domains (`/admin/settings?page=domains`). You'll see your free `<handle>.lulu.us.com` address marked Managed and Connected, and three options: "Connect existing domain", "Transfer your domain", and "Buy a new domain".
- This guide covers "Connect existing domain" — the path for a domain you already own.
- "Buy a new domain" registers a new one through Lulu with DNS and SSL already done for you — nothing to configure.
- "Transfer your domain" moves registration itself to Lulu; it's handled by the platform team as an ops request, not instantly.
2. Click "Connect existing domain" and type it in
Click "Connect existing domain", then type the domain you own (for example `shop.yourbrand.com` or your bare `yourbrand.com`) and continue. Lulu tries to detect your DNS provider automatically so it can show provider-specific instructions, or a one-click "Connect automatically" button when your provider supports it (Domain Connect).
- If one-click setup isn't available for your provider, you'll always get the manual records below — that path always works.
3. Add the www record (always)
Lulu never asks for an A record — it has no fixed IP address for your store. For a bare domain (`yourbrand.com`) or `www.yourbrand.com`, the first record is a CNAME: Name `www`, Value the routing host shown in the table (`shops.<platform-root>`). This record alone is enough for your store to work on `www.yourbrand.com`. Use the Copy button rather than retyping.
- The table's Name column uses short names (`@`, `www`, `shop`); the full name is shown under it. Most providers want the short name — if yours adds your domain automatically, typing the full name creates `www.yourbrand.com.yourbrand.com`.
- Delete any existing record named `www` (an old A or CNAME) first — the Current values column shows what is there today.
4. Add the root-domain record — or forward it to www
For the bare domain itself (Name `@`), add an ALIAS, ANAME or flattened CNAME record pointing at the same routing host. If your DNS provider doesn't offer ALIAS, ANAME or CNAME flattening for the root domain, set up domain forwarding (redirect) from `yourbrand.com` to `https://www.yourbrand.com` at your provider instead — your store then runs on www and the bare domain sends visitors there. For a subdomain (`shop.yourbrand.com`) there is only one record: a CNAME with Name `shop`.
- The `_shopwise-challenge` TXT record is optional: only add it if you can't change the records above yet. A CNAME that points at Lulu already proves you own the domain.
- Marketplace stores also add a CNAME for `admin` (admin.yourbrand.com).
5. If your DNS is on Cloudflare specifically
Add the same www and root (@) records in Cloudflare's DNS tab. We recommend leaving new records "DNS only" (grey cloud), not "Proxied" (orange cloud), at least until Lulu shows your domain connected and secured — Cloudflare's proxy sits in front of the record's real target, which can slow down or confuse domain verification and certificate issuance while you're first connecting. You can reconsider proxying afterwards once the domain is live.
6. Click "I updated DNS records" and follow the three steps
After adding the records, click "I updated DNS records". The panel shows your domain with a badge (Needs setup, Connecting, Connected or Action needed) and three steps: Configure DNS records, DNS propagation and TLS certificate. Each step reads Done (green tick), Waiting… (amber clock, with what it is waiting for) or Problem (red cross, with the exact reason, such as "www still points to 203.0.113.5"). These are status indicators, not buttons. The panel re-checks every 30 seconds while it's open; DNS changes can take up to 48 hours to spread. After setup, the Domains list keeps showing each domain's badge, a DNS / SSL health line and when it was last checked, and you can open the panel again at any time.
7. Understand how SSL actually works here
SSL (the padlock / HTTPS) is issued automatically once your DNS points at Lulu — there is no separate "enable SSL" switch and nothing to buy. The platform's edge (backed by Cloudflare) detects the correctly pointed domain, requests a certificate for every address — the root domain, www, and admin for marketplaces — using a standard domain-validation check over HTTP, and installs it. This typically takes a few minutes after DNS resolves, occasionally longer. If the "SSL & routing" check stays unchecked for a long time after "Ownership verified" is green, double-check the routing record's value and that nothing (like an aggressive Cloudflare proxy setting, or a conflicting existing A/CNAME record) is overriding it.
8. Set the domain as primary
Once the domain shows Connected, click "Set as primary" on its row. For a bare domain, www.yourbrand.com becomes the primary address by default and yourbrand.com redirects to it (this works with ALIAS or with forwarding). If you added the ALIAS record, the domain's panel lets you make the bare domain primary instead. Every other connected domain redirects to the primary one; your free `.lulu.us.com` address keeps working as a backup.
Completion checklist
- A CNAME record `www` points at the routing host Lulu shows (or, for a subdomain, a CNAME with its short name).
- The root domain (`@`) has an ALIAS/ANAME/flattened CNAME to the same host, or is forwarded to https://www.<your-domain> at your provider.
- There is no A record for www or @ left pointing at your old host.
- Settings → Domains shows the domain as Connected, with DNS ✓ and SSL ✓ in its health line.
- The domain opens over https:// with a valid padlock, with no browser warning.
- "Set as primary" has been clicked if this should be the store's main address.
Troubleshooting
My registrar won't let me put a hostname in an A record at the root domain.
Correct — an A record can only hold an IP address, and Lulu never asks for one. Add the www CNAME, then either an ALIAS/ANAME/flattened CNAME for `@`, or set up domain forwarding from the root domain to https://www.<your-domain> at your provider.
Step 1 shows Problem with an old value.
The Current values column shows what public DNS answers today. Delete the old record (an IP address or another hostname) for that name and add the one under Update to, then click "I updated DNS records".
DNS is Done but the TLS certificate is still waiting.
The certificate is issued once your addresses reach Lulu, usually minutes after propagation. The TLS step shows the certificate's state in plain words; if validation or issuance timed out, check the records and click "I updated DNS records" to request it again. If the root domain is only forwarded to www, it doesn't need a certificate — the panel says so.
Do I need to buy or upload an SSL certificate myself?
No. Once your DNS points correctly at Lulu, a certificate is requested and installed automatically for every connected address. There's nothing to buy, generate, or upload.
I use Cloudflare — should I turn on the orange-cloud proxy?
Leave new domain-connection records as "DNS only" (grey cloud) until Lulu shows the domain Connected. A proxy in front of the record can interfere with certificate issuance while you're first connecting; Cloudflare's own CNAME flattening handles the root (`@`) record.
Set up Point of Sale with one device: register, device, staff, first sale
For store owners and QA testers: install the free Lulu POS app, create a register, pair a single device, give a staff member POS access, and ring up and reconcile a first in-person sale — plus the Lite / Retail / Pro packages Point of Sale is sold under and what happens when you hit a plan's limits.
Illustrated guide: lulu.us.com/help/guide-pos-one-device
Before you startYou need access to Settings in your store admin, and at least one product in your catalog to sell. You only need ONE physical device to test the whole flow end to end — a browser on your own laptop counts as the device, there is no need for a second phone or tablet. Point of Sale is now an App Store app, “Lulu POS” (handle `shopwise-pos`): a store that hasn't added it yet is shown an install page the first time it opens Point of Sale, with three packages — Lite is free and is enough for everything in this guide.
1. Open Point of Sale (and add the app if you haven't)
In your store admin sidebar, under Sales channels, click “Point of Sale” (`/admin/pos`). This nav entry always shows. If your store hasn't added Lulu POS yet, you land on `/admin/pos/install` instead: three package cards (Lite, Retail, Pro) with their prices, device/cashier caps and feature lists, plus a line reminding you prices are per shop, in USD, on top of your plan, with 0% commission on in-person sales. Click “Add for free” on Lite — no payment method needed — and you're returned to the normal Point of Sale dashboard. At the top is the Lulu POS plan card: your package (Lite, with a Free badge), checkout devices used out of your cap, cashier accounts, and the “Upgrade” and “Manage plan” buttons (both open the app's page, `/admin/app-store/shopwise-pos`). Below it are Today's sales, any open drawer sessions, and “Open register”, which opens the actual till screen at `/pos`.
- The in-person till itself lives at `/pos`; everything under `/admin/pos/...` (Registers, Devices, Staff & PINs, Reports, Sessions) is the management side in your normal admin.
- If the store already has POS from before this app existed, it was migrated onto Lite automatically (a few were grandfathered onto Retail) — you won't see the install page at all.
2. Add a register
Go to Point of Sale → Registers (`/admin/pos/registers`) and click "Add register". A register is a checkout terminal, optionally tied to a location — stock for sales made on it is drawn from that location. Give it a name (for example "Front counter") and save.
- One register is enough to test everything in this guide.
3. Pair one device to the register
Go to Point of Sale → Devices (`/admin/pos/devices`) and click "Pair new device". Name the device (for example "Test laptop") and pick the register you just created, then click "Generate code". A 6-digit pairing code appears — it expires in 15 minutes. On the device you want to use as the till (a browser tab on the same laptop you're using right now is fine), open `/pos/pair` and type in the code.
- You only need this one device paired — there's no requirement to use a second physical machine to finish testing.
- If the code expires before you use it, go back to the device row and generate a new one.
4. What happens when you hit Lite's limits
Lite includes exactly 1 checkout device and 2 cashier accounts. If you try to pair a second device (Point of Sale → Devices → “Pair new device”) while one is already paired, you get a 422 error explaining the limit (“Lulu POS Lite includes 1 checkout device, and 1 is already paired…”) with an “Upgrade to Retail” button — the same error shows on the pairing screen itself if a code minted earlier is typed into a second browser. Giving a third non-owner staff member a PIN (or having them sign in with email and password on the till) hits the same kind of 422 for cashiers. You don't need to test this for the one-device walkthrough, but it's worth triggering once to see the upgrade prompt a merchant would see.
- If a store downgrades (trial ends, plan canceled) while it has more devices or cashiers than the new plan allows, nothing breaks immediately: there's a 7-day grace period, after which the least-recently-used devices/cashiers over the cap are automatically paused (the merchant can also choose what to keep from the plan card on the Point of Sale dashboard, or on POS → Settings, before the grace period ends).
5. Give a staff member POS access and a PIN
Staff accounts are created under Settings → Users first. Once a staff member exists, go to Point of Sale → Staff & PINs (`/admin/pos/staff`) and click "Set PIN" next to their name — a PIN is 4 to 6 digits and is stored hashed, never in plain text. This is what lets them sign in on the shared till with a quick PIN instead of their full email and password.
- "Change PIN" and "Clear PIN" are available the same way later.
- A manager can always sign in on the till with email and password instead of a PIN — useful before any PINs are set.
6. Sign in on the device and open the drawer
On the paired device, open `/pos`. Sign in either with the PIN pad (type the 4–6 digit PIN and tap Sign in) or switch to "Use email and password". Once signed in, if no drawer session is open you'll be asked to count the cash in the drawer and enter the opening float before you can start selling.
7. Ring up a test sale
Add any sample product to the cart, go to checkout, and complete payment with a cash or card tender (use test/sandbox card details if your store's payment gateway is in test mode). On the receipt screen, try both "Print receipt" and "Email receipt" if your device has a connected printer — either way the sale is recorded immediately.
- The sale appears as a normal order in Orders, tagged to your Point of Sale channel, and reduces stock at the register's location.
8. Close the session and reconcile cash
When you're done testing, close the drawer session from the till (or from Point of Sale → Sessions in admin). Count the actual cash in the drawer and enter it — Lulu compares it against the expected total (opening float plus cash sales) and shows any over or short amount. This is the cash reconciliation step a cashier does at the end of a shift.
9. Check reports
Back in admin, Point of Sale → Reports shows the sale you just made, broken out from your online sales. In Analytics, in-person Point of Sale sales appear in their own row under Sales by channel, separate from online orders and separate from any external (non-Lulu) POS connected via Settings → Apps.
10. Packages: Lite, Retail, Pro
Lulu POS is priced per shop, in USD, on top of your Lulu plan, with 0% commission on in-person sales. Lite is free, included with your plan: 1 checkout device, 2 cashier accounts, and checkout and barcode scanning · printed and email receipts · split payments and saved carts · returns at the original shop · shared online and shop stock · offline cash sales · daily sales reports and CSV export · low-stock alerts and stock counts · online order pickup. Retail is $29/month or $290/year (14-day free trial), 2 devices, unlimited cashiers, adding everything in Lite plus suppliers and purchase orders, exchanges and store credit, loyalty points and advanced promotions, staff roles and cash reconciliation, and priority support. Pro is $59/month or $590/year (14-day free trial), 4 devices, adding everything in Retail plus branch transfers and cross-branch returns, and margin and branch reports. An extra checkout device is $10/month on Retail or Pro (up to 20).
- The test in this guide only needs one device and one cashier, so it fits comfortably inside the free Lite tier.
- A “cashier account” is any active, non-owner staff member who has been given a POS PIN or has signed in to POS at least once — the owner always has access and is never counted against the cap.
- Upgrading from Lite to Retail/Pro, starting the 14-day trial, switching to yearly billing, or adding an extra checkout device are all done from the app's own page, `/admin/app-store/shopwise-pos` (reached from “Upgrade” or “Manage plan” on the plan card at the top of the Point of Sale dashboard).
Completion checklist
- A register exists under Point of Sale → Registers.
- One device shows status Paired under Point of Sale → Devices.
- A staff member has "Has POS access" and a PIN set.
- A drawer session opened with a float, and a test sale completed on `/pos`.
- The test sale appears under Orders tagged to Point of Sale, and under Point of Sale → Reports.
- Closing the session shows the cash reconciliation (expected vs. counted) screen.
Troubleshooting
The pairing code says it expired.
Pairing codes expire 15 minutes after they're generated. Go back to Point of Sale → Devices, find the device (it will show status Code expired or Pending), and click "New code" to generate a fresh one.
I only have one laptop — can I still test pairing a device?
Yes. A browser on the same computer you manage the store from counts as a device for pairing purposes — open `/pos/pair` in a separate tab or browser window and continue from there.
A staff member can't sign in on the till.
Check Point of Sale → Staff & PINs — they need "Has POS access" and a PIN set (or they can sign in with their normal email and password on the till's "Use email and password" option instead).
The sale doesn't show up in my online sales reports.
That's expected: Point of Sale sales are reported separately from online orders, in their own row under Sales by channel and in Point of Sale → Reports, so they're never mixed into online figures.
How is this different from connecting an outside POS system I already use?
This guide is about Lulu's own built-in till, now shipped as the Lulu POS app. If you run separate POS software and want it to push its sales into Lulu instead, see “Connect your in-store POS system” — that's a different connection (an access token under Settings → Apps), not a register/device pair.
I paired a device or gave out PINs and hit a “pos_limit” error.
That's the plan's device or cashier cap, not a bug — Lite includes 1 device and 2 cashiers. Either remove/unpair something you don't need, or use the “Upgrade to Retail” button in the error to see the paid tiers. If a store was recently downgraded, it gets a 7-day grace period before anything is actually paused.
Point of Sale from start to finish: locations, registers, devices, staff and your first till day
One end-to-end guide for store owners: choose a Lulu POS package, set up locations and products, create registers, pair devices, add staff with PINs and location access, set offline rules, then open, sell, refund, close and reconcile a till day — with what each package allows.
Illustrated guide: lulu.us.com/help/guide-pos-complete-setup
Before you startYou need the store owner account, or a role that can manage Point of Sale, users and settings. Have at least one product and one location. One device is enough to try everything here: a browser on your own laptop counts. This guide links the steps together. For more detail on checkout, discounts and receipts see “Point of Sale: run a till day”, and for scanning see “Barcode scanning in POS without a scanner”.
1. Plan your setup in this order
Point of Sale works best when you set it up in the same order the till depends on it. 1) Add the Lulu POS app and pick a package. 2) Check your locations under Settings → Locations. 3) Make sure the products you sell in the shop are Active and published to Point of Sale. 4) Create a register for each counter and give it a location. 5) Pair a device to each register. 6) Add your staff, give them POS access and a PIN, and (on Retail or Pro) choose where they may sign in. 7) Set receipts, payment types and offline rules under Point of Sale → Settings. 8) Open the register with a float and ring up a small cash test sale, then close it and check Reports.
- The Point of Sale dashboard (`/admin/pos`) has a “Setup checklist” that ticks off Location set, Register created, Device paired, Staff PIN set, Receipt configured and Tipping configured as you go.
- Everything under `/admin/pos/...` is the back office. The till itself is a separate screen at `/pos`.
2. Add the app and choose a package
Open Point of Sale in your admin sidebar. If the app isn't added yet you land on the install page with three packages. Lite is free and included with your plan: 1 checkout device and 2 cashier accounts. Retail is $29/month or $290/year (14-day free trial): 2 checkout devices and unlimited cashiers. Pro is $59/month or $590/year (14-day free trial): 4 checkout devices and unlimited cashiers. On Retail and Pro you can add an extra checkout device for $10/month each, up to 20. Click “Add for free” for Lite, or “Start free trial” for Retail or Pro.
- What the packages change at the till: Retail adds exchanges and refunds to store credit, the register Hardware settings (USB or serial receipt printer and cash drawer) and per-location staff access. Pro adds returns of sales made at another location and the “By location” branch report.
- Prices are in USD, per shop, on top of your Lulu plan, with 0% commission on in-person sales.
- There is no limit on the number of registers. Only checkout devices and cashier accounts count against your package.
- You can upgrade, start a trial or add a device later from “Upgrade” or “Manage plan” on the Lulu POS plan card at the top of the dashboard.
3. Check your locations
Every register sells from a location: stock is taken from there, and tax is worked out from that location's address. Create your shops and warehouses under Settings → Locations (“Add location”). Then open Point of Sale → Settings and, under Location, choose a “Default location”. It is “Used when a register has no location of its own”.
- A register set to “No location” sells from the default location. If you never chose one, Lulu uses your oldest location.
- Give each register its own location if you have more than one shop. Stock checks, returns and the branch report all follow the register's location.
4. Get products ready for the till
The register finds a product only when it is Active and published to the Point of Sale channel. In the product's “Publishing” card, under “Sales channels and apps”, tick “Point of Sale”. To change many products at once, select them on the Products list and use “Publish to…”. Then put stock where you sell it: on the variant's “Inventory” card, type the quantity into “Available” on the row for the register's location. If the stock is sitting at another location, move it under Products → Transfers (“Create transfer”, then “Mark as in transit” and “Receive items”).
- Publishing is store-wide. You can't show a product at one shop's register and hide it at another's. What differs per location is stock: an item with no stock at the register's location still shows, and the cart warns, for example ““Classic Tee” is out of stock at Galle Road — 12 available at Main store”. It's a warning, not a block. You can still sell it, and that location's stock goes below zero.
- Prices are the same at every location. The register uses the variant's price; there are no per-location prices. Discounts limited to a market don't apply at the till, because the register has no market.
- Give every variant a barcode or SKU so it can be scanned. See “Barcode scanning in POS without a scanner”.
5. Create a register for each counter
Go to Point of Sale → Registers and click “Add register”. Enter a “Register name” (for example “Front counter”) and choose its “Location”. Under “Register settings” you can override the “Tip prompt” and “Default grid mode”, and tick “Auto-print receipt after a sale”. On Retail and Pro, the “Hardware” section sets the printer connection (Browser print, USB or Serial), paper width, copies, auto-cut and cash drawer, and “Test print” checks it. Click “Save”.
- Click a register in the list to rename it, change its location or make it inactive. You can't make a register inactive while it has an open session (“Close the open session on this register before deactivating it.”).
- USB and serial printers work in Chrome or Edge on a computer or Android device. iPad uses browser printing. On Lite, receipts always print through the browser.
6. Pair a device to the register
Go to Point of Sale → Devices and click “Pair new device”. Type a “Device name” (for example “Front counter iPad”), pick the “Register”, and click “Generate code”. A 6-digit pairing code appears. It works once and expires in 15 minutes. On the device you want to use as the till, open `/pos/pair` on the same admin address, type the code under “Pairing code” and tap “Pair device”. The device now belongs to that register, and through it to that location and your store.
- If you chose “No register yet (assign with Edit before pairing)”, the Devices list shows “No register — can’t pair yet” and the code is refused on the device (“This pairing code isn’t linked to a register yet…”). Click “Edit” on the device, choose a “Register” and “Save”. The same code then works, as long as it hasn't expired.
- “Edit” on the Devices list also renames a device (“Device name”), and moves a paired device to another register. The move takes effect on the device's next action: it then sells from the new register's location and uses its drawer session. Sync its offline sales first (on the device: More → “Offline sales”). Any still waiting are sent later but booked on the new register.
- Any up-to-date browser works: a laptop, a desktop, an Android tablet or an iPad. The register can also be installed as an app from the browser's “Install app” or “Add to Home Screen” option. Open `/pos` while you are online the first time so the device can save the screens it needs.
- Pairing lasts a year on that browser. If you clear the browser's data or use a private window, the device has to be paired again.
- Pairing signs out whoever was signed in on that browser before, so the next person always signs in fresh.
- Several devices can share one register. They share the register's single cash drawer session, but each device keeps its own cart. For separate cash counts, give each counter its own register.
- If you reach your package's device limit, pairing is refused with a message such as “Lulu POS Lite includes 1 checkout device, and 1 is already paired…”. Upgrade, add a checkout device (Retail and Pro), or revoke a device you no longer use.
7. If a device is paired to a different store
A browser is paired to one store's register at a time. If you open the register from your admin (“Open register”) on a browser that is still paired to another store's register, for example a store you also manage, the till does not open. You see “This device is paired to another store” with that store's name, and nothing from the other store is shown. Choose “Pair this device to …” to move it to your store: you'll need a new code from Point of Sale → Devices, and staff sign in again afterwards. If your store has no register yet, the button reads “Set up a register for …” and takes you to Registers first. Choose “Keep using …” if the device really belongs to the other store: whoever was signed in on it is signed out (or the screen is locked) first, and that store's staff then sign in with their own PIN.
- “Pair this device to …” is switched off while sales made offline on the other store's register are still waiting to sync. Keep using that store until they've synced, then move the device.
- Sales saved offline are kept separately for each store, and the saved catalog for each register. Neither is ever shown on, or sent through, another store's register.
- If you open the register from the admin while offline, the till can't confirm which store the device belongs to. It asks you to reconnect instead of showing a saved catalog.
- If your admin sign-in has ended, “Open register” shows “Sign in to the admin again” and nothing else. Sign in, then click “Open register” again.
8. Add staff and give them POS access
Add people under Settings → Users (the Users page) with “Add staff”. If they only work the till, choose “POS-only staff” under “Type of user” (“Point of Sale only, with POS roles. No staff seat.”) and give them a POS role that can use the register, such as “POS full permissions”. POS-only staff can't sign in to the admin at all, only to the register. For someone who also works in the admin, choose “Store staff”. Then go to Point of Sale → Staff & PINs. Click “Give POS full access” for anyone showing “No POS access”, and “Set PIN” to give them a 4–6 digit PIN. Click “Save PIN”.
- Managed POS roles: “POS administrator” (every POS feature plus device setup, POS users and POS roles), “POS full permissions” (every register feature plus POS user management), “POS user administrator” (adds and removes POS-only users and makes basic sales) and “POS device setup” (pairs devices only and can't use the till). A store user who holds only POS roles sees the Point of Sale pages their role allows, for example Devices for device setup or Staff & PINs for POS user management.
- A cashier account is any non-owner staff member who has a PIN or has signed in at the till. Lite includes 2. Retail and Pro are unlimited. The store owner is never counted.
- Only the store owner or someone with “Manage POS users” can set another person's PIN. There's no self-service PIN screen at the till, so a cashier who forgets their PIN asks a manager to “Change PIN” on Staff & PINs.
- Partner collaborators (the “Collaborator” rows on Staff & PINs) can't use Point of Sale. Their access never includes POS permissions, so these rows show “Collaborators can’t use Point of Sale” instead of the PIN and access buttons. If a partner also works your till, add them as a staff member with their own account.
9. Choose where each person can sign in (Retail and Pro)
On Point of Sale → Staff & PINs, click “Edit locations” next to a staff member. For each location, tick “Can sign in here”, and optionally pick a location role in place of their “Store-wide role”. Click “Save locations”. Once a location has at least one person ticked, only the people ticked there can sign in to that location's registers. Everyone else sees “You don’t have access to the register at this location. Ask a manager.”
- A location role can only narrow or reshape someone's POS permissions at that location. It never gives POS access to someone who has none.
- The store owner and Administrators can always sign in everywhere (“All locations (owner)”).
- On Lite the rows are locked (“Available on Retail”): everyone with POS access can sign in at every register.
10. Set receipts, payments and offline rules
Open Point of Sale → Settings. Set the receipt header and footer, the tip prompt, your “Payment types” (Cash, Card for your own card terminal, Gift card, Store credit, Bank transfer, Mobile wallet and your own custom types), and any “Required checkout information”. Under “Offline sales”, decide whether to “Allow offline card charges” and set a “Per-transaction offline cap” (0 means no cap). Click “Save settings”.
- The register never charges a card itself. “Card” records a payment you took on your own card terminal, with its reference number.
- Offline, the register takes only cash, card payments recorded from your terminal (when “Allow offline card charges” is on) and your custom payment types, up to the offline cap. Gift cards, store credit, Mintpay, bank transfer and mobile wallet need a connection. Offline cash sales are included on the Retail and Pro packages.
- Queued sales sync on their own when the connection is back. You can also open More → “Offline sales” on the till to “Retry” them. The register warns you when a sale has waited over 24 hours, and again after 72 hours.
11. Sign in at the till
On the paired device, open `/pos`. The sign-in screen shows the register's name and location (“… · Sign in to take the till”), six PIN dots and a number pad. A cashier types their PIN and taps “Sign in”, or taps “Use email and password” to sign in with their account. Its footer says which device this is: “Paired to … Ask a manager to re-pair this device from Point of sale → Devices.” From the admin, the “Open register” button on the Point of Sale dashboard opens the same till.
- After 5 wrong PINs in 15 minutes on one device, PIN sign-in on that device is locked for 15 minutes (manager-approval PINs have their own 5). Other tills keep working. As protection against guessing, PIN entry on all of the store's tills is also locked after 30 wrong PINs in 15 minutes, sign-in and approval PINs counted together. Wait, or sign in with “Use email and password”.
- The same person can be signed in on two devices at once. Each device still has one cashier at a time.
- A cashier stays signed in for up to 14 days, or until they sign out or are switched. The till does not lock or sign out by itself when idle: lock it from the avatar menu (“Lock the register”) when you step away. Only the same person's PIN unlocks it with the cart still there (“Sign in as someone else” signs out instead).
- Removing someone's POS role, suspending them or clearing their PIN takes effect on their next action at the till.
12. Hand over the till mid-shift
To change cashier without closing the drawer, open the avatar menu and choose “Switch staff”, then the next person types their PIN and taps “Switch”. The register says “Signed in as …”. The drawer session keeps running, because it belongs to the register, not the person. A sale in progress stays in the cart, and sales rung up from now on are credited to the new cashier.
- To credit a sale to someone else, use “Attribute sale” in the cart's ⋯ menu (needs “Manage sales attribution for orders”).
13. Open the drawer with a float
If no drawer is open, the till shows “No register session is open. Open one to track cash in the drawer.” Tap “Open register”, count the cash under “Cash in the drawer now” (or tap “Use last close · …”), add a note if you like, and tap “Open register · …”. That amount is the opening float.
- Opening and closing the drawer needs “Start and end payment tracking sessions”. A register has one open session at a time, shared by every device on that register.
14. Sell, refund and move cash during the day
Add items by search, scan, the Grid, the Library or the Keypad, then tap “Checkout · …”, take the payment and choose a receipt. For a refund, open More → “Returns and exchanges”, find the order, choose the items and whether to restock at this location, then pick where the money goes: “Original payment”, “Cash”, “Store credit” or “Gift card”. A cash refund is paid out of the open drawer. For cash added or taken out, open More → “Register session” and use “Pay in”, “Pay out” or “Drop”, each with an “Amount” and a “Reason”.
- Returns at the shop where the sale was made are included on every package. Exchanges and refunds to store credit need Retail. Returning a sale made at another location needs Pro, and the items are restocked at the location doing the return.
- “Return without receipt” refunds only to store credit or a gift card, never cash.
- See “Point of Sale: run a till day” for every checkout, discount and receipt option.
15. Close the drawer and check the difference
At the end of the day, on More → “Register session”, tap “Close register”. Count the drawer and enter it as “Cash counted”. “Expected in drawer” stays hidden until you tap “Show”, so the count is blind. Expected cash is the opening float plus cash sales and pay-ins, minus cash refunds, pay-outs and drops. The till then shows “Drawer balances”, “Over” or “Short” with the difference. Add a note explaining any difference and tap “Close register”. A closed session can't be reopened.
- In the admin, Point of Sale → Sessions lists every session with its “Variance”. A manager can close a forgotten session there with “Close session”.
16. Read the reports
Point of Sale → Reports shows in-person sales for “Today”, “Last 7 days”, “Last 30 days” or “Last 90 days”. Filter by register and staff with “All registers” and “All staff”. The tiles are “Net sales”, “Orders”, “Average sale”, “Tips”, “Refunds”, “Discounts” and “Tax collected”, followed by “By tender”, “By staff”, “By register”, “By hour” and “Cash drawer movements”. Click “Export CSV” to download.
- “By staff” and “By register” are on every package. “By location”, and filtering to one location, are on Pro (“Available on Pro”). Below Pro, all locations show together as one row.
- In-person sales also appear in Orders and in Analytics under Sales by channel.
17. Removing a device or going over your package
To retire a device, go to Point of Sale → Devices and click “Revoke”. The browser is signed out of the register at once and shows the pairing screen. A drawer session that is open on its register stays open, and can be closed from another device on the same register, from the admin, or after re-pairing. Sales the device still holds offline stay on it and sync only once it is paired to a register of the same store again, so let them sync before you revoke. If your package drops (for example a trial ends) and you have more devices or cashiers than it allows, everything keeps working for 7 days. After that, the extra devices show “Paused (over plan limit)” and the extra cashiers can't sign in. Choose what to keep with “Choose what to keep” on the plan card.
- A paused device keeps its pairing, so nothing needs re-pairing when you upgrade. A sale made offline before the pause is still accepted for up to 72 hours.
- Sales a device saved offline before an earlier update, whose register can't be confirmed, are held and listed as “… offline sales from an earlier pairing can’t be sent — contact support” rather than sent to another register.
- Revoking frees a device slot right away. “Re-pair” on a revoked device gives a new code.
Completion checklist
- Lulu POS is added, and the plan card shows the package you need.
- Every shop exists under Settings → Locations, and a Default location is chosen in Point of Sale → Settings.
- Products to sell are Active, published to Point of Sale, and stocked at the register's location.
- Each counter has a register with its own location.
- Each till device shows “Paired” under Point of Sale → Devices, on the right register.
- Each cashier has POS access and a PIN (and, on Retail or Pro, the right locations).
- Offline rules and payment types are saved in Point of Sale → Settings.
- A drawer was opened with a float, a test sale and a test refund went through, and closing showed the variance.
- The test sale appears in Point of Sale → Reports and in Sessions.
Troubleshooting
I clicked “Open register” and saw another store's products and prices.
That browser was still paired to another store's register. The till now stops on “This device is paired to another store” and shows nothing from that store. Choose “Pair this device to …” to move the device to your store with a new code from Point of sale → Devices, or “Keep using …” if the device belongs to the other store.
“Open register” sends me to the pairing screen.
This browser isn't paired to a register in your store yet. If your store has no register, the pairing screen says so and links to Registers. Create one, then get a code from Point of Sale → Devices.
A product shows at the till but says it is out of stock.
Stock is counted per location. Put stock at the register's location on the variant's Inventory card, or move it with a transfer. You can still sell it, and that location's stock goes below zero.
A product doesn't appear at the till at all.
Check it is Active and that “Point of Sale” is ticked in its Publishing card. Publishing applies to every register in the store.
Can I charge a different price at one shop?
No. The register uses the variant's price at every location. Use a discount at the till if one sale needs a different price.
A cashier gets “You don’t have access to the register at this location.”
Someone is ticked under “Edit locations” for that location, and this cashier isn't. Tick “Can sign in here” for them on Point of Sale → Staff & PINs.
Nobody can sign in with a PIN.
After 5 wrong PINs in 15 minutes on one device, that device's PIN sign-in is locked for 15 minutes; other devices still work. If 30 wrong PINs were typed across the store's tills in 15 minutes, every till waits 15 minutes. Wait, or sign in with “Use email and password”.
The offline queue says “… offline sales from an earlier pairing can’t be sent — contact support”.
These sales were saved on the device before an update and the register can't prove which store they belong to, so they are held instead of being sent to the wrong one. On More → “Offline sales”, use “Download held sales” to keep a copy. If you're sure they belong to this store, “Send to this store…” sends them, booked on this register, once the store owner or an administrator enters their PIN. Send them while you're online: the approval is checked again when each sale arrives and lasts 5 minutes. A sale that is refused goes back on hold. Otherwise contact support, and don't clear the browser's data.
The offline queue says sales “from another store’s register can’t be sent here”.
Those sales were made while this device was paired to another store. They are only ever sent to that store, once the device is paired to it again. Use “Download” to keep a copy. The pairing screen also warns you when a device still holds unsent sales.
I want to rename a device or change its register.
On Point of Sale → Devices, click “Edit” on the device, change “Device name” or “Register”, and click “Save”.
I can't set a PIN for a partner collaborator.
Collaborators can't use Point of Sale. Add the person as a staff member (or POS-only staff) with their own account instead.
Pairing a second device fails with a limit message.
Lite includes 1 checkout device, Retail 2 and Pro 4. Revoke one you don't use, upgrade, or add an extra checkout device on Retail or Pro ($10/month).
Can two devices use the same register?
Yes. They share the register's cash drawer session and each has its own cart. For separate cash counts, create a register per counter.
Point of Sale: run a till day
A full in-store trading day on the Lulu POS register, from the morning set-up to the end-of-day count: stock at the right location, products on the Point of Sale channel, staff PINs and roles, opening the drawer, selling, taking payment, receipts, returns and exchanges, cash in and out, closing with an over/short count, and the reports afterwards.
Illustrated guide: lulu.us.com/help/guide-pos-till-day
Before you startThis guide assumes the Lulu POS app is already added and one device is paired. If not, follow “Set up Point of Sale with one device” first: it covers adding the app (“Lulu POS”, handle `shopwise-pos`), creating a register, pairing a device at `/pos/pair` and giving a staff member a PIN. You need the store owner account or a role with the Point of Sale and inventory permissions. Some steps depend on your Lulu POS package (Lite, Retail or Pro); each step says so where it matters.
1. Check the app and the register's location
Open Point of Sale in your admin sidebar (`/admin/pos`). If you land on the install page, click “Add for free” on Lite, then continue with “Set up Point of Sale with one device”. Next, go to Point of Sale → Registers (`/admin/pos/registers`) and open the register you'll use today. Its “Location” decides where every sale on it takes stock from. A register set to “No location” uses the “Default location” from Point of Sale → Settings (“Used when a register has no location of its own”).
- Locations themselves are created under Settings → Locations (“Add location”).
- Before you open the till, check that the register's location is the shop it physically stands in. Stock and the “out of stock” checks in the next step all follow it.
2. Put stock at that location (and fix “out of stock at this location”)
The register only sells what is in stock at its own location. If a product's quantity is tracked, it doesn't allow overselling, and the register's location holds none, the cart shows a warning such as ““Product name” is out of stock at Galle Road — 12 available at Main store”, or “Only 2 of “Product name” are in stock at Galle Road — 9 more at Main store” when you ask for more than there is. It's a warning, not a block: you can still charge the sale, and that location's stock goes below zero (as in Shopify POS). Stock elsewhere is named so you know where to fetch it, but it isn't sold from here. To fix it, open the product, then the variant (`/admin/products/…/variants/…`). In the “Inventory” card, with “Track quantity” on, the table lists every location with “Committed”, “Available” and “On hand”. Type the quantity into “Available” on the register's row and save. Alternatively, go to Products → Inventory (`/admin/inventory`), pick the location in the location selector (not “All locations”), click the Available number for the item, choose “Set to” or “Adjust by”, and “Save”.
- “Continue selling when out of stock” on the variant lets the register sell below zero. Use it for made-to-order items, not as a quick fix for stock that really is at another shop.
- If you turn “Track quantity” off, the register never checks stock for that variant.
- Changing quantities needs the “Manage inventory” permission. Without it, the variant page says “You can view quantities. Ask a store admin for “Manage inventory” to change them.”
3. Move stock between locations with a transfer
If the stock exists but sits at another location (a warehouse or another branch), move it rather than typing new numbers. Go to Products → Transfers (`/admin/transfers`) and click “Create transfer”. Choose the “Origin” and the “Destination” (the register's location), click “Add product” to add the items and quantities, and save it (“Save as draft”). When the goods leave, click “Mark as in transit”. When they arrive at the shop, open the transfer and click “Receive items”. The received quantity becomes available at the destination, and the register can sell it.
- The Transfers page needs the transfers permission (view or manage). It is part of your admin and isn't locked to a POS package.
- Lulu POS Pro lists “Branch transfers and cross-branch returns”. On the till itself, Pro is what allows a return of a sale made at another location (see the returns step).
4. Make sure products are published to Point of Sale
The register's search, Library, tiles and barcode scans only find products that are Active and published to the Point of Sale channel. Open a product and look at the “Publishing” card. Under “Sales channels and apps”, tick “Point of Sale” and save. The card says “This product is draft, so it isn’t visible on any channel until you set it to Active” when the status is the problem. To change many products at once, select them on the Products list and use “Publish to…”, pick Point of Sale and click “Publish” (“Unpublish from…” does the reverse).
- A product you have never changed publishing for is available on every channel, Point of Sale included. Only a product someone unticked (or scheduled) is hidden from the till.
- Each channel row also has “Schedule” (“Publish on” / “Unpublish on”) if a product should only appear at the till from a given date.
5. Staff, PINs, POS roles and location access
People are added under Settings → Users and permissions, which links to the Users page (`/admin/staff`), and roles live on its Roles tab. Built-in POS roles are “POS administrator”, “POS full permissions”, “POS user administrator” and “POS device setup”. A custom role created as a “POS role” holds only Point of Sale permissions. The permissions that matter on a till day include “Apply custom discounts”, “Apply discount codes”, “Add custom sales”, “Edit taxes”, “Redeem store credit”, “Return and exchange orders”, “Create unverified returns”, “Cancel”, “Open drawer”, “Start and end payment tracking sessions” and “Manager approval”. Then go to Point of Sale → Staff & PINs (`/admin/pos/staff`). Use “Give POS full access” for someone with “No POS access”, and “Set PIN” to give them a 4–6 digit PIN.
- “Edit locations” on Staff & PINs lets you choose where each person “Can sign in here”, with an optional location role in place of their “Store-wide role” at that location. This per-location access needs Lulu POS Retail or Pro; on Lite the rows are locked.
- The store owner always shows “All locations (owner)”.
6. How manager approval works at the till
When a cashier tries something their role doesn't allow, the register opens a “Manager PIN” pad instead of just refusing. This covers actions at checkout and on orders, such as tax exempt, a return, voiding a sale or a cross-location order lookup. A custom discount works differently: a cashier without “Apply custom discounts” sees “You don’t have permission to apply custom discounts. Ask a manager to approve it.” and “Apply” stays off, so a manager signs in on the register (switch user) to apply it, or you add the permission to the cashier's role. The default line is “A manager needs to approve this action.” A manager types their own PIN and taps “Approve”. It only works if that manager holds “Manager approval” and the permission being approved, at this register's location. The approval is single use, lasts at most 5 minutes, and is tied to that cashier, that register and (where the screen knows it) that order or amount. The approver is recorded.
- There is no separate “price override” on a line. To sell an item for less, apply a custom discount to the line (next steps), which falls under “Apply custom discounts”.
- If the PIN is wrong or the manager lacks the permission, the pad says “That PIN wasn’t recognized”.
7. Sign in and open the register with a float
On the paired device, open `/pos` and “Sign in” with your PIN, or tap “Use email and password”. If no drawer is open, a banner says “No register session is open. Open one to track cash in the drawer.” Tap “Open register”, count the cash under “Cash in the drawer now” (or tap “Use last close · amount” to reuse yesterday's closing count), add an optional note, and tap “Open register · amount”. That amount is the opening float.
- Opening and closing the drawer needs “Start and end payment tracking sessions”.
8. Ring up items: Grid, Library, Keypad and search
The top of the register has the search bar (“Search or scan to add items”) and three modes. “Grid” shows your smart-grid tiles, which can be products, collections, discounts, fees, links and actions such as “Add custom sale” or “Add gift card”. “Library” browses collections and products, with “Favorites”. “Keypad” is for a custom amount: type it, optionally fill “Name (optional)” (it defaults to “Custom sale”), choose “Charge tax on this amount”, and tap “Add to cart”. Custom sales need “Add custom sales”. Without it, the keypad says “You don’t have permission to add custom sales. Ask a manager to approve it.” Tap a cart line to change “Quantity”, add a line note, or apply a line discount.
- Search by name, or scan or type a barcode. See “Barcode scanning in POS without a scanner” for exactly how codes are matched.
- A product with several variants opens a variant picker. A single-variant product goes straight into the cart.
9. Customer, discounts, notes and tax exempt
Tap “Add customer” in the cart to search (“Search or scan customers”) or “Create customer” (name, email, phone, marketing consent). Under the cart lines are three quick chips. “Add discount” opens “Percentage”, “Amount” or “Code”, with an optional “Reason (optional)”, then “Apply”. “Tax exempt” removes tax from the whole sale. “Add note” takes an order note, saved with “Save note”. For a single line, tap it and choose “Apply custom discount”, or type a line “Note” (“Prints on the receipt”). The ⋯ “Cart actions” menu adds “Attribute sale” (credit the sale to a staff member), “Add service charge”, “Saved carts” and “Ship all items”.
- Percentage and amount discounts are custom discounts (“Apply custom discounts”). A code uses “Apply discount codes”. “Tax exempt” needs “Edit taxes”. Without the right permission the manager-approval pad appears.
- “Remove line discount” and “Remove discount” undo them.
10. Park a sale with Saved carts
If a customer steps away, tap “Save cart” under the cart, give it a “Name” and save it. The cart clears for the next customer. To pick it up again, open “Saved carts” (from the ⋯ menu, the More menu or the Library shortcut) and choose it. Saved carts don't hold stock, and any register in this store can open them. Deleting one (“Delete cart”) removes it for every register.
- Saved carts are part of the Retail and Pro packages, and use the “Manage saved carts” permission.
11. Take payment: cash, card, split and other tenders
Tap “Checkout · total”. Choose a tender. For “Cash”, enter “Cash received” or tap a quick amount (the first is marked “Exact”); the screen shows “Change due” and you tap “Accept” (the button shows the cash taken). For “Card”, charge the customer on your own card terminal (“Charge this on the card terminal, then record it below.”), then fill “Amount taken on the card”, “Card type”, “Last 4 digits” and “Terminal reference”, and tap “Record” (the button shows the amount). For a split, enter less than the total on one tender: the rest shows as “Remaining after this payment”, the header changes to “Split payment”, and you pick the next tender for the remainder. When everything is covered, tap “Complete sale · total”.
- Other tenders appear when they're switched on under Point of Sale → Settings → “Payment types”. They are “Gift card” (scan or type the code, “Check balance”, “Redeem”), “Store credit” (only with a customer attached; needs “Redeem store credit”), “Bank transfer”, “Mobile wallet”, your own custom payment types, and “Custom…” for a cheque or voucher.
- “Mintpay” (pay in 3 by QR code or SMS link) appears only when Mintpay is set up under Settings → Payments.
- If “Show a tip prompt at payment” is on in Point of Sale → Settings, the customer is offered a tip first.
- The card tender only records a payment taken on a separate terminal. The register does not charge cards itself.
12. Give a receipt
After the sale the register asks “How would you like the receipt?”. “Email” sends it to the customer's address (you can type another and tap “Send receipt”). “Print” uses the browser's 80 mm print view, or the USB/serial receipt printer set on the register. “No receipt” skips it. Then tap “New sale”.
- “Text message” is shown, but Lulu has no SMS gateway yet. The request is logged and no text is actually sent, so use email or print.
- Email and text need a connection (“Needs a connection” when offline). Printing works offline.
- To print automatically after every sale, tick “Auto-print receipt after a sale” on the register.
13. Returns and exchanges
Open More → “Returns and exchanges” (`/pos/returns`). Under “Find the order”, scan the receipt's barcode or search by order number, customer or item, then pick the order. Choose the items and quantities, an optional “Return reason”, and whether to “Restock at (this location)”. Tap “Next · amount”, check the “Return summary”, choose where the money goes (“Original payment”, “Cash”, “Store credit” or “Gift card”), add the “Refund approval number” if you refunded on the card terminal, and tap “Refund” (the button shows the amount). For an exchange, tap “Exchange” instead of Next. The return becomes “Exchange credit” on a new sale at the register, and the customer pays or gets back only the difference.
- Package rules: a return to the original shop is on every package (Lite included). Exchanges and refunds to store credit need Retail. Returning a sale that was made at a different location needs Pro. Otherwise the till shows “Available on Retail — upgrade Lulu POS to use this” (or Pro).
- “Return without receipt” refunds only to “Store credit” or “Gift card”. Because that counts as store credit, it also needs Retail and the “Create unverified returns” permission.
- Returns need “Return and exchange orders”. Without it, a manager can approve with their PIN.
14. Cash in and out during the day
Open More → “Register session” (`/pos/session`). “Current drawer” shows “Starting cash”, “Cash sales”, “Paid in”, “Paid out & drops”, “Cash refunds” and the running “Expected in drawer”. Use “Pay in” for cash added (a float top-up), “Pay out” for petty cash taken out, and “Drop” for cash moved to the safe or bank. Each asks for an “Amount” and a “Reason”. Every movement is listed under “Drawer activity”.
15. Close the register and count the cash
At the end of the day, on `/pos/session` tap “Close register”. Count the drawer and enter it as “Cash counted”. “Expected in drawer” stays hidden until you tap “Show”, so the count is blind. The register then shows “Drawer balances”, “Over” or “Short” with the difference. Add a note (it asks you to “explain the difference” when there is one) and tap “Close register”. This cannot be undone once the session is closed.
- A manager can also close a forgotten session from the admin: Point of Sale → Sessions → the session → “Close session”, entering “Counted cash”. This needs “End payment tracking sessions from the admin”.
16. Review the day: Reports and Sessions
In the admin, Point of Sale → Reports (`/admin/pos/reports`) shows in-person sales for “Today”, “Last 7 days”, “Last 30 days” or “Last 90 days”. You can filter by location, register and staff. The page shows “Net sales”, “Orders”, “Average sale”, “Tips”, “Refunds”, “Discounts” and “Tax collected”, with tables “By tender”, “By staff”, “By register” and “By hour”, plus “Cash drawer movements”. “Export CSV” downloads the data. Point of Sale → Sessions lists every drawer session with its “Variance”. Open one to see the “Cash ledger”, tenders, staff and the orders taken on it.
- “By location” (branch reports) is “Available on Pro”.
- “External POS sales” lists sales pushed in by your own POS system through the Admin API, kept out of the register figures.
Completion checklist
- The register's “Location” (or the POS “Default location”) is the shop it stands in.
- Products you sell are Active and ticked for “Point of Sale” in their “Publishing” card.
- Stock is set (or transferred and received) at the register's location.
- Each cashier has POS access, a PIN, and a role with the permissions they need; at least one manager has “Manager approval”.
- The drawer was opened with a counted float.
- A test sale was completed with cash (change due shown) and a receipt emailed or printed.
- A return was processed from `/pos/returns`.
- The drawer was closed with a blind count, and the session shows its variance under Point of Sale → Sessions.
- Point of Sale → Reports shows the day, and “Export CSV” downloads it.
Troubleshooting
The cart says ““…” is out of stock at …”, but the product has stock.
The stock is at a different location. The register only counts the location set on it (or the POS “Default location” when the register has none). Set the quantity for that location on the variant's “Inventory” card or in Products → Inventory with that location selected, or move stock with Products → Transfers → “Create transfer”, then “Mark as in transit” and “Receive items”. For made-to-order items, tick “Continue selling when out of stock” instead.
A product doesn't appear in the register's search or Library.
Check that it is Active and that “Point of Sale” is ticked in its “Publishing” card, or that a “Publish on” schedule hasn't been set for a later date. Draft and archived products never appear on the till.
A cashier can't apply a custom discount (“Apply” stays off).
Their role lacks “Apply custom discounts” (or “Apply discount codes” for a code). Either a manager signs in on the register and applies it, or you add the permission to the cashier's role on the Users page's Roles tab. Staff with “POS full permissions”, administrators and the owner can always apply custom discounts.
“Returns and exchanges” is greyed out, or a return is refused with an upgrade message.
Returns at the original shop are included in every package. Exchanges and store-credit refunds need Retail, and returns of sales from another location need Pro. The refusal message names the package you need. Until then you can still refund the order from the admin under Orders.
The customer didn't receive a text-message receipt.
SMS receipts aren't available yet: there is no SMS gateway, so the request is only logged. Send the receipt by email or print it.
The drawer is short or over at close.
Check “Drawer activity” on `/pos/session` (or the “Cash ledger” on the session in admin) for pay-outs, drops and cash refunds that weren't counted. Record the reason in the close note. The variance stays on the session for reporting.
Barcode scanning in POS without a scanner
How the Lulu POS register reads barcodes: typing a code and pressing Enter, plugging in a USB or Bluetooth scanner, what the scan icon in the search bar does, where to set barcodes on products, how to print barcode labels, and scanning gift cards, customer cards, discount codes and receipts.
Illustrated guide: lulu.us.com/help/guide-pos-barcode-scanning
Before you startYou need the Lulu POS register open at `/pos` on a paired device (see “Set up Point of Sale with one device”), and products that are Active and published to the Point of Sale channel. A barcode scanner is optional: everything in this guide also works by typing the code on the keyboard.
1. Give your products a barcode (or a SKU)
The register looks codes up in two fields on each variant. For a product with one variant, open the product and, in the inventory area, open the “Barcode” chip to fill “Barcode (ISBN, UPC, GTIN, etc.)”, or the “SKU” chip to fill “SKU (Stock Keeping Unit)”. For a product with options, open each variant (`/admin/products/…/variants/…`) and fill the same two fields in its “Inventory” card. Save.
- Use the number printed under the manufacturer's barcode (UPC/EAN/ISBN) if the item has one. If it doesn't, a SKU works too, because the register also accepts an exact SKU.
- Give every variant its own code. If two variants share the same barcode, a scan returns only one of them, and the register gives no way to choose.
2. Without a scanner: type the code and press Enter
Click into the register's search bar (“Search or scan to add items”), type the barcode or SKU, and press Enter. If the typed text matches no product name, the register looks the code up exactly: first against variant barcodes, then against SKUs. A match is added straight to the cart, one unit at a time with no confirmation. If nothing matches, the register shows “No product matches barcode (the code)”.
- Codes must match exactly as saved on the variant. Part of a code doesn't match.
- The live results list under the search bar searches product names (and vendor), not barcodes. If your typed code also appears in a product title, that product is listed, and Enter adds the highlighted result instead of doing the barcode lookup. Use the arrow keys to move the highlight, or make sure codes don't look like product names.
- Only Active products published to Point of Sale can be found, by name or by code.
3. With a USB or Bluetooth scanner
Most handheld scanners act as a keyboard: they type the code very fast and finish with Enter. The register listens for that pattern anywhere on the selling screen, so you don't need to click into the search bar first. A burst of at least 4 characters, typed with less than about 60 milliseconds between keys and ending in Enter, is treated as a scan and looked up exactly like a typed code. Ordinary typing is slower, so it is never mistaken for a scan.
- Set the scanner to send an Enter (carriage return) after each code. Most do by default; check its manual if scans type the code but nothing is added.
- Pair a Bluetooth scanner in the device's own Bluetooth settings, as a keyboard. Nothing needs to be set up in Lulu.
- A code shorter than 4 characters isn't caught as a scan. Type it and press Enter instead.
4. What the scan icon in the search bar does
The icon at the right of the search bar (“Scan a barcode”) doesn't open the camera. It shows a reminder under the bar: “Scan with the counter scanner, or type the barcode and press Enter.” The register cannot read barcodes with a phone or tablet camera today. Without a scanner, type the code as in the previous step.
5. Print barcode labels for your shelves and stock
Go to Point of Sale → Labels (`/admin/pos/labels`, “Print labels”). Under “Add products”, search by product title and tick the variants you need. Set how many labels each gets (1–500) in the “Selected” list. Pick a “Template”: “2.25 × 1.25 in roll”, “1.5 × 1 in roll” or “A4 sheet (3 × 8 = 24/page)”. Under “Fields”, choose what to print: “Title”, “Variant”, “Price”, “Barcode” and “SKU”. Then click “Print … labels”, which opens your browser's print dialog.
- Labels carry a Code 128 barcode of the variant's barcode, or of its SKU when it has no barcode. So every label scans back to the right variant at the register.
- Printing goes through the browser, so use your label printer's driver and paper size in the print dialog.
6. Scan a gift card at checkout
At checkout, choose the “Gift card” tender. The “Gift card code” field (“Scan or type the code”) is focused, and a scan is caught wherever the focus is on that screen. The balance is checked straight away and shows “Card balance” and “Applied to this sale”. Tap “Redeem” to use it, and if the balance doesn't cover the sale, pay the rest with another tender. Typing works too: enter the code and press Enter or tap “Check balance”.
- Gift card codes are 8 to 20 letters and digits. Spaces and dashes from a printed voucher are ignored.
- A 2D scanner reading the QR of the gift card email's balance link works too: the register takes the code out of the link.
- Customers can show their card as a barcode from your store's gift card balance page (“Show code as barcode”, with the note “Show this at the till — the cashier can scan it to pay in store.”).
- Scanning something that isn't a gift card here shows “That barcode isn’t a gift card code”.
7. Scan a customer's in-store card
Signed-in customers have an “In-store customer card” on their account page: a barcode with a code like `C-1234-56`. At the register, tap “Add customer”. While the “Add customer” sheet is open (“Search or scan customers”), scan the card. If exactly one customer matches, they're attached to the sale at once. Otherwise the scanned value becomes the search and the matching customers are listed. The same scan lookup works for an exact email address or phone number.
- Without a scanner, type the card code, email or phone into the search field and pick the customer from the list.
8. Discount codes and receipts
In “Add discount”, the “Code” option says “Type it, or scan the customer’s QR code with the counter scanner.” Click into the “Discount code” field and scan or type the code, then tap “Apply”. For returns, the receipt printed from the register's 80 mm print view carries a barcode of the order number. On “Return or exchange” (`/pos/returns`), scan it into the “Scan the receipt, or search order number, customer or item” field, or type the order number, and pick the order from the results.
- Mintpay is the other way round: “Print payment slip” prints a QR code that the customer scans with the Mintpay app to pay. The register itself doesn't scan it.
Completion checklist
- Every variant you sell has a unique “Barcode (ISBN, UPC, GTIN, etc.)” or SKU.
- Typing a known barcode into the search bar and pressing Enter adds the item to the cart.
- An unknown code shows “No product matches barcode …”.
- If you use a scanner, it sends Enter after each code and a scan adds the item without clicking the search bar.
- Labels print from `/admin/pos/labels`, and a printed label scans back to the right variant.
- A gift card code is accepted on the “Gift card” tender, and a customer card attaches the customer in “Add customer”.
Troubleshooting
“No product matches barcode …” but the product exists.
Check that the code is saved exactly (no extra characters) in the variant's “Barcode (ISBN, UPC, GTIN, etc.)” or “SKU” field, and that the product is Active and ticked for “Point of Sale” in its “Publishing” card. Products not published to Point of Sale can't be scanned.
Pressing Enter added the wrong product.
When the typed text also matches a product name, Enter adds the highlighted search result rather than doing the barcode lookup. Clear the field and scan, or give products codes that don't appear in their titles. If two variants share one barcode, give each its own.
My scanner types the code into the field but nothing is added.
The scanner probably isn't sending Enter at the end. Turn on its carriage-return / Enter suffix (see the scanner's manual). Codes shorter than 4 characters aren't caught as scans; press Enter yourself after them.
The scan icon doesn't open my camera.
That's expected: the register has no camera scanning, and the icon only shows a reminder. Use a USB or Bluetooth scanner, or type the code and press Enter.
The scanned item says it is out of stock.
The scan worked. The register's location has no stock for that item. See “Point of Sale: run a till day” for setting stock per location or transferring it.
A gift card scan says “That barcode isn’t a gift card code”.
The scanned value isn't 8–20 letters and digits (or a gift card balance link). Check you scanned the gift card, not a product, or type the code printed on the card.
Connect Facebook & Instagram (catalog feed)
For store owners: install the free Facebook & Instagram app, turn on the catalog feed, add it in Meta Commerce Manager, and confirm every product and variant is syncing — plus what this does and doesn't do today.
Illustrated guide: lulu.us.com/help/guide-facebook-instagram-channel
Before you startYou need access to Settings in your store admin, and a Meta Business Suite / Commerce Manager account (free to create) with a Facebook Page and, optionally, an Instagram account connected to it. Facebook & Instagram is a free App Store app (handle `facebook-instagram-channel`) — install it first if your store hasn't already. No Meta app review or developer account is needed for the feed itself — it's a standard scheduled catalog feed, the same mechanism most catalog-feed apps use.
1. Install the app and open Sales channels → Facebook & Instagram
In your admin sidebar, under Sales channels, click “Facebook & Instagram” (`/admin/channels/facebook`). If the app isn't installed yet, you'll see a card titled “Install Facebook & Instagram from the App Store (free)” with an “Install Facebook & Instagram” button — click it, no payment method needed. Once installed, the page explains the honest scope up front: Lulu publishes a standards-based Meta commerce catalog feed of your products; you connect it once in Meta Commerce Manager and Meta refetches it on its own schedule. Direct API sync and on-Facebook/Instagram checkout need Meta's own app review and access tokens, which isn't part of this feed-based connection.
2. Turn on the feed (Meta IDs are optional)
Toggle "Enable the Facebook & Instagram feed" on and click Save. Your feed URL answers only while the app is installed and this toggle is saved on — turn it off and save, and the URL answers "not found", so Meta can no longer update your catalog. The Meta Business ID and Catalog ID fields are optional: the feed doesn't need them, because Meta reads your products from the feed URL. Paste them once your catalog exists in Commerce Manager, for your records, and optionally a Meta Pixel ID for conversion tracking reference.
- No catalog yet? Leave the ID fields empty, add the feed in Commerce Manager (step 4), then come back and paste the IDs in if you want them on record.
- The ID fields accept numbers only — copy them exactly as Commerce Manager shows them.
3. Copy or preview your feed URL
Under "Your catalog feed URL" you'll see your store's feed address at `/feeds/meta-catalog.xml` on your store's primary address — your connected custom domain, or your store's free address if you haven't connected one — so Meta fetches it directly, with no redirect. Use Copy to grab it, or Preview to open it directly and confirm it returns your product data (not an error page) before pasting it into Meta. If the feed is off, the page says so above the URL and Preview shows "not found".
4. Add the feed in Meta Commerce Manager
Open Meta Commerce Manager (business.facebook.com/commerce) and create, or open, a catalog of type E-commerce. In the catalog, open Data sources and add items from a data file using a URL — Meta currently labels this Add → Data file → Use a URL or Google Sheets (older accounts show Add items → Use a URL / scheduled feed). Paste your Lulu feed URL and set a refresh schedule — daily is fine for most stores. No field mapping is needed: the feed already uses Meta's standard `id`, `title`, `description`, `price`, `sale_price`, `availability` and `item_group_id` attributes.
- Each size, colour or other variant is sent as its own item, linked to its product by `item_group_id`, so shoppers can pick a variant on Facebook and Instagram. The item opens your product page with that variant already selected.
- A product on sale is sent with its regular (compare-at) price as `price` and the price you charge as `sale_price`, so Meta shows the regular price crossed out.
- Every item has its own ID: the variant's SKU when no other variant uses that SKU, otherwise a Lulu ID. Give every variant its own SKU to keep your SKUs as the IDs.
5. Connect your Page and turn on Shops
Still in Commerce Manager, connect your Facebook Page and Instagram account to the catalog, then turn on Shops so products can be tagged in posts, Reels, and Stories. This step happens entirely on Meta's side.
6. Test that products are syncing
Back on the Lulu Facebook & Instagram page, the side panel shows how many of your products are "feed-ready" out of your total catalog, and how many feed items they become — one per variant, so this number is usually higher than your product count. It lists the reasons any products can't be listed yet (for example no price, no image, no description — Meta requires a description — or a starter sample product that still says “Replace this sample with your own product”) and warns about listed products Meta may flag (for example no brand, a SKU shared with another variant, or a placeholder stock photo such as picsum.photos instead of a real product photo). In Commerce Manager, check the catalog's item count matches Lulu's feed-item count, that products show their variants, and that items are Active (not Rejected or Pending review).
- A product can take a few minutes to a few hours to appear in Commerce Manager after the first scheduled fetch runs.
- Lulu never fills in made-up values: a product with no vendor is sent without a brand, and a product with no description isn't listed until you add one.
Completion checklist
- Facebook & Instagram shows installed (Sales channels → Facebook & Instagram, or App Store → Facebook & Instagram → “Manage app”).
- The "Enable the Facebook & Instagram feed" toggle is on and saved, and the page shows a live feed URL on your store's own address.
- Previewing the feed URL directly returns product data, not a 404 or empty page.
- The feed is added as a scheduled data source in Meta Commerce Manager, under an E-commerce catalog.
- The feed-item count on Lulu matches the item count Meta reports, and products with sizes or colours show their variants in Meta.
- The feed-ready panel shows no warnings you haven't reviewed (missing brand, shared SKU).
- A Facebook Page (and Instagram account, if used) is connected to the catalog with Shops turned on.
Troubleshooting
The Facebook & Instagram page just shows an install card, not the feed settings.
The app isn't installed on this store yet. Click “Install Facebook & Instagram” on that card (it's free, no payment method needed) and the normal feed settings page appears.
Meta says it can't fetch the feed URL.
Make sure the Facebook & Instagram app is installed and the "Enable the Facebook & Instagram feed" toggle is on and saved — the feed URL only answers while both are true, and answers "not found" otherwise. Also check you copied the full URL including `https://`. Preview the URL yourself first to confirm it loads.
Some products aren't in the feed.
Check the "feed-ready" panel on the channel page — products without a price, without images, without a description, that are a draft/archived status, that aren't published to Facebook & Instagram, or that are still a starter sample product (the description says “Replace this sample with your own product”) are excluded until you fix them. A product with no brand (vendor) also needs a barcode or SKU on its variants, because Meta requires a brand, GTIN or MPN.
Meta rejects items with "Content ID is duplicate".
Lulu no longer sends two items with the same ID: when two variants share a SKU, both are sent with a Lulu ID instead and the feed-ready panel warns "SKU used by more than one variant". Give each variant its own SKU (Products → the product → the variant) so your SKUs become the IDs again. Meta treats an item whose ID changed as a new item.
Meta shows the sale price as the regular price.
The feed sends one `price` (the regular compare-at price) and one `sale_price` for every product on sale. If Meta still shows the old price, wait for the next scheduled fetch, or run a manual fetch from the data source in Commerce Manager.
Can customers check out directly inside Facebook or Instagram?
Not through this connection. On-platform checkout and deeper API sync require Meta's own app review and access tokens, which Lulu's feed-based connection doesn't include. Today, tapping a product in Shops takes the shopper to your store to buy.
How often does Meta refresh my catalog?
Whatever schedule you set for the scheduled feed in Commerce Manager (daily is typical). Lulu's feed itself is always current when fetched — the delay is only how often Meta chooses to refetch it.
Connect Google & YouTube (Merchant Center feed)
For store owners: install the free Google & YouTube app, turn on the product feed, add it in Google Merchant Center, and confirm every product and variant is syncing — plus what this does and doesn't do today.
Illustrated guide: lulu.us.com/help/guide-google-youtube-channel
Before you startYou need access to Settings in your store admin, and a free Google Merchant Center account (merchants.google.com) with your storefront domain verified and claimed. Google & YouTube is a free App Store app (handle `google-youtube-channel`) — install it first if your store hasn't already. No Google API credentials or developer account are needed for the feed itself — it's a standard scheduled product feed, the same mechanism most feed apps use.
1. Install the app and open Sales channels → Google & YouTube
In your admin sidebar, under Sales channels, click “Google & YouTube” (`/admin/channels/google`). If the app isn't installed yet, you'll see a card titled “Install Google & YouTube from the App Store (free)” with an “Install Google & YouTube” button — click it, no payment method needed. Once installed, the page explains the honest scope up front: Lulu publishes a standards-based Google Merchant Center product feed; you add it once in Merchant Center and Google keeps your products current from it, powering free product listings, Shopping, and YouTube surfaces. Direct Content API sync and Buy-on-Google checkout need Google API credentials, which isn't part of this feed-based connection.
2. Turn on the feed (Merchant Center ID is optional)
Toggle "Enable the Google & YouTube feed" on and click Save. Your feed URL answers only while the app is installed and this toggle is saved on — turn it off and save, and the URL answers "not found", so Google can no longer update your products. The Merchant Center ID field is optional: the feed doesn't need it, because Google reads your products from the feed URL. Paste it in for your own reference (find it in Merchant Center → Settings) once you've created an account.
3. Copy or preview your feed URL
Under "Your product feed URL" you'll see your store's feed address at `/feeds/google-merchant.xml` on your store's primary address — your connected custom domain, or your store's free address if you haven't connected one. That is the domain to verify and claim in Merchant Center (next step). Use Copy to grab it, or Preview to open it directly and confirm it returns your product data before pasting it into Merchant Center. If the feed is off, the page says so above the URL and Preview shows "not found".
4. Verify and claim your site in Merchant Center
Open Google Merchant Center and create an account if you don't have one. Verify and claim your store's website (your storefront domain) — Merchant Center requires this before it will accept a feed for that domain.
5. Add the feed as a scheduled fetch
In Merchant Center, go to Products → Feeds → Add primary feed, and choose "Scheduled fetch". Paste your Lulu feed URL and set a daily fetch schedule. The feed already uses Google's standard `g:id`, `g:title`, `g:description`, `g:price`, `g:sale_price`, `g:availability` and `g:item_group_id` attributes, so no field mapping is needed.
- Each size, colour or other variant is sent as its own item, linked to its product by `g:item_group_id`, with its own `g:size` / `g:color` (also `g:material` / `g:pattern`) taken from options with those names. The item opens your product page with that variant already selected.
- A product on sale is sent with its regular (compare-at) price as `g:price` and the price you charge as `g:sale_price`.
- Every item has its own ID: the variant's SKU when no other variant uses that SKU, otherwise a Lulu ID. Give every variant its own SKU to keep your SKUs as the IDs.
- A product with no vendor is sent without `g:brand` (never a placeholder). If it also has no barcode, it's marked `g:identifier_exists` = no, which is how Google expects custom or handmade goods without a GTIN to be sent.
6. Turn on free listings and Shopping
Once the feed is accepted, turn on free listings in Merchant Center (and Shopping ads if you plan to run paid campaigns). Paste your Merchant Center account ID back into the Lulu page for your own records, if you haven't already.
7. Test that products are syncing
On the Lulu Google & YouTube page, the side panel shows how many products are feed-ready, how many feed items they become (one per variant), the reasons any products can't be listed (for example no price, no image, no description — Google requires a description — or a starter sample product that still says “Replace this sample with your own product”) and warnings for listed products Google may flag (for example no brand, a SKU shared with another variant, a variant option Google can't read, or a placeholder stock photo such as picsum.photos instead of a real product photo). In Merchant Center, check Products → Diagnostics for your item count and any disapproved items (common causes: missing GTIN/brand, low-quality images, or price mismatches with your site). Confirm the item count matches Lulu's feed-item count, and that your products start appearing in free listings within a day or two of the first successful fetch.
Completion checklist
- Google & YouTube shows installed (Sales channels → Google & YouTube, or App Store → Google & YouTube → “Manage app”).
- The "Enable the Google & YouTube feed" toggle is on and saved, and the page shows a live feed URL on your store's own address.
- Previewing the feed URL directly returns product data, not a 404 or empty page.
- Your storefront domain (the one in the feed URL) is verified and claimed in Google Merchant Center.
- The feed is added as a scheduled primary feed in Merchant Center and its item count matches the feed-item count on Lulu.
- The feed-ready panel shows no warnings you haven't reviewed (missing brand, shared SKU, variant options).
- Free listings (and Shopping ads, if used) are turned on.
Troubleshooting
The Google & YouTube page just shows an install card, not the feed settings.
The app isn't installed on this store yet. Click “Install Google & YouTube” on that card (it's free, no payment method needed) and the normal feed settings page appears.
Merchant Center rejects the feed or shows 0 items.
Make sure the Google & YouTube app is installed and the "Enable the Google & YouTube feed" toggle is on and saved — the feed URL only answers while both are true, and answers "not found" otherwise. Also check you copied the full `https://` URL, and that the domain in that URL is verified and claimed in Merchant Center first — an unclaimed domain is the most common reason a feed is rejected outright.
Some products are disapproved.
Check Products → Diagnostics in Merchant Center for the specific reason (common ones: missing brand/GTIN, image too small, price mismatch with the live product page), and the warnings in the feed-ready panel on the Lulu page. Fix the product in Lulu and wait for the next scheduled fetch, or trigger a manual fetch from Merchant Center.
My variants don't show as separate sizes or colours.
Google reads variants from options named Size, Color (or Colour), Material or Pattern. A product whose options have other names (for example "Style") is still sent one item per variant, but the feed-ready panel warns that Google may not tell those variants apart — rename the option if one of those names fits.
Can shoppers buy directly inside Google or YouTube?
Not through this connection. Buy-on-Google checkout and deeper Content API sync need Google API credentials, which this feed-based connection doesn't include. Today, a tap on a listing takes the shopper to your store to buy.
How long until my products show up in search?
Once the feed is accepted, free listings typically start appearing within a day or two, though it can take longer for a brand-new Merchant Center account to build trust.
Let AI channels discover your products (Agentic)
For store owners and QA testers: turn on Agentic discovery, understand the open product feed, llms.txt and MCP endpoint that power it, choose which AI channels may read your store (switching one off blocks its crawlers in robots.txt), and fix the listing problems the quality score flags.
Illustrated guide: lulu.us.com/help/guide-agentic-ai-channels
Before you startYou need access to Settings in your store admin. There's nothing to connect on a third-party site for this one — Agentic publishes an open, standards-based feed that any compliant AI agent can already read; it doesn't need a partnership or developer account with any AI provider.
1. Open Sales channels → Agentic
In your admin sidebar, under Sales channels, click "Agentic" (`/admin/agentic`). The page is upfront about scope: Lulu publishes an open, machine-readable agent product catalog plus `llms.txt`, so assistants like ChatGPT, Google AI Mode/Gemini, Microsoft Copilot, Meta AI, Perplexity, and Claude can find, understand, and cite your products. What's guaranteed is the open feed and standards below — being placed *inside* a specific assistant's own shopping surface needs that provider's own partnership, which is outside Lulu's control.
2. Turn on Discovery
Toggle "Let AI channels discover my products" on. This publishes your public agent catalog feed; while it's off the feed URL returns a 404 and no product data is exposed. Leave the "Lulu Catalog — publish the open product feed" toggle on underneath it (it's the schema.org product/offer feed agents actually crawl for prices, stock and images) — turning Discovery on but Catalog off still blocks the feed.
- "Auto-enroll new AI channels as they become available" turns on newly supported channels for you automatically as Lulu adds them, so you don't have to come back and flip each one on by hand.
3. Choose which AI channels may read your store
Below Discovery, toggle individual channels — ChatGPT, Google AI Mode & Gemini, Microsoft Copilot, Meta AI, and "Other agents (Perplexity, Claude, etc.)" — on or off, then click Save. All five start on. Switching a channel off adds that provider's AI crawlers to your store's `robots.txt` as Disallow, and each channel's note says exactly which ones. `robots.txt` is a request that reputable crawlers follow, not a lock — the feed, `llms.txt` and the MCP endpoint stay public URLs while at least one channel is on.
- ChatGPT off: GPTBot, OAI-SearchBot and ChatGPT-User are disallowed.
- Google AI Mode & Gemini off: Google-Extended is disallowed. Googlebot keeps indexing you for Search, so AI Overviews can still cite your pages.
- Microsoft Copilot off: Microsoft has no separate AI crawler — Copilot answers from Bing's index — so your pages carry a `noarchive` header instead (Bing's signal to keep them out of Copilot answers). Bing search is unaffected.
- Meta AI off: meta-externalagent and meta-externalfetcher are disallowed. Link previews when someone shares your product still work.
- Other agents off: ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Applebot-Extended, Amazonbot, Bytespider and CCBot are disallowed.
- Every channel off: the catalog feed, `llms.txt` and the MCP endpoint close too, and the feed card says "Every AI channel is switched off".
- The robots.txt preview under Online Store → SEO & AI shows the effect of these switches (the bot list there shows only the blocks you set on that page).
4. Check your feed, llms.txt, and the MCP endpoint
The page shows your live feed URL with Copy and Open buttons — this is your store's `/feeds/agent-catalog.json`. It also points to `/llms.txt` for agent hints. Separately (not shown on this settings page, but documented for developers), the store exposes an MCP endpoint at `/api/mcp` that lets MCP-compatible agents query your catalog programmatically rather than just reading the static feed.
- The MCP endpoint is a developer-facing detail — most merchants only need to confirm the feed URL and llms.txt open correctly.
- Image links in the feed and in MCP results are full addresses on your store's domain, so agents can load your uploaded photos.
- `llms.txt` lists your collections, your newest products (while the feed is live), a link only to the policies you have written, and a Contact section built from your Contact information policy (Settings → Policies). A cleared or empty policy is never linked, and its page answers "not found".
- The feed carries the same policy links and contact details. Only text you published in the Contact information policy is used — your private store email and phone from Settings → General are never exposed.
5. Confirm the feed URL and status on your own store host
The sidebar's “Agent catalog feed” card shows an Enabled/Disabled pill plus your store's real feed URL — built from your store's own host (custom domain if you have one, otherwise your `.lulu.us.com` address), never the shared admin host. Use the Open button to load it directly; it should return product JSON when the pill says Enabled. The canonical URL is `/feeds/agent-catalog.json`; the same feed also answers without the `.json` suffix at `/feeds/agent-catalog`, for agents that expect either form.
- When the pill says Disabled, the feed still answers with a clear reason instead of a bare 404: a JSON body `{"error":"agentic_disabled","hint":…}`. The note under the pill says whether Discovery, the Lulu Catalog toggle, or every AI channel being off is the cause.
- The “How AI channels discover your products” card underneath explains the three pieces together: the catalog feed, `/llms.txt`, and the `/api/mcp` endpoint for MCP-aware agents.
6. Check product listing quality
The Listing quality card scores how "agent-ready" each active product is, from its description (100+ words is full marks), attributes (price, product type, vendor and a SKU on every variant), real images (3 or more — placeholder stock photos count for nothing), variants and stock, plus a small share for your store policies. A product with a blocking problem can't score above Fair (55), however good the rest is. A warning banner above the list counts the problems across all your active products, and each product lists its own.
- Blocking (caps the score): a sample product, placeholder images (picsum.photos and similar stock-photo services), no images, no description, or a SKU another product also uses.
- Warnings: a variant without a SKU, no brand (vendor), no category (product type), or out of stock.
- Sample products — the starter products whose description still says "Replace this sample with your own product" — are left out of the agent feed, MCP search, llms.txt and the Facebook & Instagram and Google & YouTube feeds until you rewrite or archive them. They stay on your storefront.
- The image count is exactly what the feed sends agents: still images only, not videos or 3D models.
- A policy counts as written only when it has visible text — a policy you cleared in Settings → Policies shows as Missing.
7. Watch for agentic orders in your reports
Any order that arrives tagged as coming from an AI agent is attributed to the `agentic` channel in your reports, the same way Point of Sale or online orders get their own channel — so once this is live you can see whether it's actually driving sales.
- An agent's checkout link opens your normal cart. Its Estimated total includes the estimated shipping shown above it (free when the cart qualifies for free shipping); checkout still prices the real rate for the shopper's address.
Completion checklist
- "Let AI channels discover my products" and "Lulu Catalog" are both on, and at least one AI channel is on.
- Opening `https://<your-store-host>/feeds/agent-catalog.json` directly (on the store host, not the admin host) returns product JSON, not a 404.
- `https://<your-store-host>/llms.txt` opens, lists your store, and links only policies you have written.
- `https://<your-store-host>/robots.txt` disallows the crawlers of any channel you switched off.
- The Listing quality warning banner shows no sample products, placeholder images or duplicate SKUs you haven't dealt with.
Troubleshooting
The feed URL on the Agentic page shows a 404.
Check the Enabled/Disabled pill next to “Agent catalog feed” first — Disabled means Discovery or the Lulu Catalog toggle is off, and the feed answers a JSON `{"error":"agentic_disabled"}` by design, not a bug. If the pill says Enabled and it still 404s, confirm you're opening the URL shown on the page (your store's own host), not a different domain.
Discovery is on but the feed still 404s even on my store host.
Check that "Lulu Catalog — publish the open product feed" is also on underneath the master Discovery toggle — turning Discovery on alone isn't enough if Catalog is off.
I switched a channel off but its assistant still mentions my store.
The switch asks that provider's crawlers to stay away through `robots.txt`; reputable crawlers follow it on their next visit, but it doesn't remove what they already know, and it is a request rather than access control. Google AI Overviews and Copilot answer from the normal Google and Bing search indexes, which the switches deliberately leave alone so you stay in search. To close the feed, `llms.txt` and MCP entirely, switch every channel off or turn Discovery off.
A product isn't in the agent feed.
Check that it is active and published to the AI shopping agents channel, and that it isn't a sample product — a description that still says "Replace this sample with your own product" keeps it out of the feed, MCP search and llms.txt. Rewrite the description (or archive the sample) and it is included.
llms.txt doesn't link my Terms of service (or another policy).
A policy is linked only once it has content. Write it in Settings → Policies and save; an empty or cleared policy is left out on purpose, because its page answers "not found".
Will turning this on get my store featured inside ChatGPT or Gemini's own shopping results?
Not by itself. This guarantees an open, readable feed that any standards-compliant agent can use today. Being placed inside a specific assistant's own closed shopping surface needs that provider's own partnership and onboarding, which Lulu doesn't control.
What is `/api/mcp` and do I need to do anything with it?
It's a developer-facing endpoint that lets MCP-compatible AI agents query your catalog directly instead of only reading the static feed file. Most merchants don't need to configure anything for it — it's there for developers building deeper agent integrations.
My agent-ready score is low even though my products look fine.
Read the issues listed under the product. Placeholder stock photos, a SKU shared with another product, a missing description, or a leftover sample product each cap the score at 55 (Fair); a missing product type, brand or SKU, fewer than three real images, or an out-of-stock variant lower it.
Sell on Amazon, eBay and Etsy (Marketplace Connect)
For store owners and QA testers: what the Marketplaces page shows today, how the Marketplace Connect app (free while your store is in development) and its paid Unlimited sync tier work, why Amazon, eBay and Etsy say “Coming soon”, and how to connect and test a marketplace once a platform administrator has enabled it.
Illustrated guide: lulu.us.com/help/guide-marketplaces-amazon-ebay-etsy
Before you startMarketplaces is backed by an App Store app, “Marketplace Connect” (handle `feedsync-marketplace-channels`) — free while your store is in development, with paid upgrades. You can browse the page and see each marketplace's status without it — the read view is open — but connecting, syncing and managing listings need the app installed. On a development store you can install it free; on a live store, installing starts a 14-day trial of the paid “Unlimited sync” tier ($99), because the free tier is development-store-only. On top of that, each marketplace needs its own developer application credentials added by a platform administrator in the platform console before any store can connect to it at all — until that happens, every store sees the same “Coming soon” state described below.
1. Open Sales channels → Marketplaces
In your admin sidebar, under Sales channels, click “Marketplaces” (`/admin/channels/marketplaces`). This page is readable even without the Marketplace Connect app installed. You'll see a card for Amazon, eBay, and Etsy — click a marketplace's name (or “View details”) to open its own page — each with a status badge: “Coming soon” (the platform hasn't enabled this marketplace yet), “Not connected” (enabled, but you haven't connected your seller account), “Connected”, or “Reconnect needed”/“Attention” if something went wrong with an existing connection.
2. Understand why it says "Coming soon"
Each marketplace needs its own developer application registered with Lulu (an SP-API app for Amazon, equivalent developer apps for eBay and Etsy) before any store can connect a seller account through it. A card showing "Coming soon" means a platform administrator hasn't added that marketplace's Client ID / App ID / Client Secret in the platform console (Marketplace Channels, under Super) yet. Clicking into a "Coming soon" card opens that marketplace's page, which shows the same "Coming soon" badge and the same explanation: "[Marketplace] connections are not enabled on this platform yet. The platform operator must add the [marketplace] developer credentials in the platform console (Marketplace Channels)." Its Sync activity section stays hidden until the marketplace is enabled.
- This is an important, deliberately-built feature, not a placeholder page — the connect flow, listings sync, bulk listing tools, and order import described below already exist; they're just gated behind the platform operator completing a one-time setup per marketplace, and behind the Marketplace Connect app itself for the write actions (connect, sync, publish, messages, reviews).
3. Install Marketplace Connect (and the live-store trial)
Click “Install Marketplace Connect” (development store) or “Choose a plan” (live store) on the install card — a live store cannot pick the free tier directly, because it's development-store-only; choosing a plan there starts a 14-day trial of Unlimited sync ($99/month) instead. Bulk listing management and cross-region marketplace pricing are Unlimited sync features; the base connect/sync/order-import flow works on the free (dev-store) tier too.
- A store that already had a marketplace connection before this app existed was auto-installed at the free tier by the migration, so it keeps working without a surprise trial.
4. Once enabled: connect your seller account
When a marketplace's card shows "Not connected" instead of "Coming soon", click into it and click "Connect". This sends you through that marketplace's own OAuth authorization flow (sign in to your Amazon Seller Central / eBay / Etsy account and approve access), then returns you to Lulu with the seller account linked.
5. Test listing sync
On a connected marketplace's page, open the Listings tab. Search or filter by listing state, select one or more products, and publish them — each result shows success or failure per item, with failed items retryable individually. Bulk actions (Unpublish, Set price override, Set quantity buffer) are available from the same toolbar; very large bulk operations may require the store's Growth plan, shown as an upgrade banner if you're below it.
6. Test order import
Open the Orders tab on the connected marketplace's page. Place or simulate a test order on the marketplace itself (most offer a sandbox/test-order mode), then confirm it appears here and as a normal order in your main Orders list, tagged to that marketplace channel.
7. Check Messages and Reviews
If the marketplace supports it, the Messages tab surfaces buyer messages from that marketplace inside Lulu, and Reviews shows marketplace reviews for your listings. Not every marketplace's API supports every tab — a tab shows a note like "[Marketplace] does not support publishing listings through its API" when a capability isn't available there.
8. Cross-region pricing and the "Marketplace Connect" app
For stores selling into multiple marketplace regions, cross-region pricing lets you set different prices per marketplace/region rather than syncing one flat price everywhere. Cross-region pricing is an Unlimited sync feature. This whole feature area — connect, sync, bulk tools, order import, cross-region pricing — comes from the Marketplace Connect app (made by Lulu, installed from the App Store), just as it does on Shopify: the Marketplaces page under Sales channels is where you use it, but connecting, syncing and listing need the app installed (steps 2–3).
Completion checklist
- Marketplace Connect is installed (free on a development store; a live store is on its 14-day Unlimited sync trial or a paid plan).
- The platform administrator has added that marketplace's developer credentials in the Super console (Marketplace Channels), so the card no longer shows "Coming soon".
- A seller account is connected via OAuth and the card shows "Connected".
- At least one product publishes successfully to the marketplace from the Listings tab.
- A test order placed on the marketplace appears in both the marketplace's Orders tab and the main Orders list.
- Messages/Reviews show real data where that marketplace's API supports them.
Troubleshooting
Every marketplace shows "Coming soon" and there's no Connect button anywhere.
That's expected until a platform administrator adds that marketplace's developer credentials in the Super console. There's nothing to configure on the store side until then — ask the platform admin to complete that one-time setup per marketplace.
Connect fails partway through the OAuth flow.
Make sure you're signed in to the correct seller account on the marketplace's own site before starting, and that the seller account is in good standing there (suspended or unverified seller accounts are often rejected by the marketplace itself, not by Lulu).
A bulk publish action is greyed out or shows an upgrade banner.
Large bulk listing operations can require the store's Growth plan. Either reduce the batch size, or upgrade the plan if you need to manage listings at scale.
A tab (Messages, Reviews, or Listings) is missing or shows a notice.
Not every marketplace's API exposes every capability — the page shows a note explaining which capability that marketplace doesn't support rather than hiding the tab silently.
On a live store, I can't install Marketplace Connect for free.
That's expected — the free tier is development-store-only. On a live store, installing starts a 14-day trial of the paid Unlimited sync tier instead; use a development store if you specifically need to test the free tier.
Shipping: buy labels, or connect ShipStation / Shippo
For store owners and QA testers: buy and print a shipping label from an order using the built-in Shippo integration, or connect your own ShipStation or Shippo account — plus which countries and carriers are realistically supported, and who gets charged what.
Illustrated guide: lulu.us.com/help/guide-shipping-labels-shipstation-shippo
Before you startShipping lives under Admin → Sales channels → Shipping (`/admin/shipping`), not Settings. ShipStation and Shippo are both free App Store apps — install the one you want before you can use its page; a store without the app sees a one-click install card instead of a 404. There is no platform-wide Shippo account: shipping labels are always bought through the merchant's own connected Shippo account, so install Shippo first if you want to buy a label at all. You need at least one test order to work through this guide.
1. Open Admin → Sales channels → Shipping
In admin, go to Sales channels → Shipping, or directly to `/admin/shipping`. The page lists Shippo, ShipStation, and a “Shipping labels” summary card. The subtitle is upfront: “Lulu charges nothing for these — you pay the provider directly for postage and products.” Each provider card shows a Connect or Manage button once its app is installed; without the app, opening ShipStation or Shippo's own page shows an install card (“Install ShipStation/Shippo from the App Store (free)”) instead.
2. Install Shippo, then connect your account (for buying labels inside Lulu)
Open Shippo (`/admin/shipping/shippo`). If the app isn't installed yet, click “Install Shippo” on the install card first — it's free, no payment method needed; there is no platform Shippo account, so this step is required before you can buy any label. Then create a free account at portal.goshippo.com if you don't have one, go to API → create a token there, paste it into the “Shippo API token” field and click “Connect Shippo”. A token starting `shippo_test_` puts the store in Test mode automatically — test labels are watermarked “SAMPLE - DO NOT MAIL” and can't actually be used to ship a parcel, which is exactly what you want for a QA pass.
- Shippo shows the token once — paste it in straight away.
- Under "Carrier accounts", activate carriers (USPS, UPS, FedEx, DHL, and others) in your Shippo dashboard, then click "Refresh carriers" here to pull them in. Carriers created with a test token only exist in test mode.
3. Place a test order, then buy a label from it
Place or pick a test order and open it in admin. A "Shipping label" card appears above the fulfilment form (only once Shippo is connected). Choose the "Ship from" location, a package size (or Custom size with length/width/height in cm), and total weight in grams, then select which unfulfilled items and quantities to ship. Click "Get rates" to fetch live carrier rates for that exact parcel, pick a rate, optionally tick "Send shipment details to the customer", and click "Buy label".
- Shippo charges this to your own Shippo account — Lulu itself charges nothing for the label.
- If you change the parcel or items after getting rates, you'll be asked to "Refresh rates" — a label always prices exactly what's shown on screen.
4. Confirm tracking, fulfilled status, and the shipping email
After buying, the label appears on the order with a tracking number (clickable if a tracking URL is available), and you can "Print label" or download the commercial invoice if one was generated. The shipped items move to fulfilled, and — if you left "Send shipment details to the customer" ticked — the customer receives a shipping confirmation email with the tracking number.
- Under Settings → Shipping and delivery → Shipping labels (`/admin/shipping/labels`), the label shows up in the list with its cost, carrier/service, and order — useful for checking label spend across many test orders at once.
5. Install and connect ShipStation (for pushing orders into your own ShipStation account)
Open ShipStation (`/admin/shipping/shipstation`). If the app isn't installed yet, click “Install ShipStation” on the install card first — it's free. The recommended mode is “Custom Store” — ShipStation pulls your orders on its own schedule and posts tracking back, with no ShipStation API key needed, and it works on every ShipStation plan. Choose Custom Store and click “Connect”; Lulu then shows your Custom Store credentials: the “URL to custom XML page” (copy this), a Username, and a one-time Password shown once (copy it immediately — it can't be retrieved later, only regenerated). In ShipStation, go to Settings → Selling Channels → Store Setup → Connect a Custom Store, and paste the URL, username and password there.
- An "API key" mode is also offered for stores on a ShipStation Standard plan or higher, if you'd rather send orders to ShipStation yourself from the orders list instead of letting it pull on a schedule.
6. Test that orders and tracking sync with ShipStation
In ShipStation, trigger a refresh of your Custom Store connection (or wait for its next scheduled pull) and confirm your test order appears there. Create a label for it inside ShipStation. Back in Lulu, use "Test connection" on the ShipStation page to confirm the link is healthy, and check that the order picks up the tracking number and moves to fulfilled once ShipStation posts it back.
7. Countries, carriers, and who gets charged
Shippo's labels (USPS, UPS, FedEx, DHL, and others depending on what you activate in Shippo) are mainly built around US-origin and international shipments; coverage for a non-US origin depends entirely on which carriers Shippo and ShipStation support shipping from that country. A Sri Lankan store can connect a Shippo or ShipStation account the same way any store does, but whether any carrier actually offers labels from a Sri Lankan origin address depends on the carriers you activate inside Shippo/ShipStation themselves — check your Shippo dashboard's available carrier accounts for your specific origin before relying on this for a non-US store. In every case: Lulu charges nothing for shipping labels or for connecting ShipStation/Shippo — Shippo bills your own Shippo account directly for postage, and ShipStation is billed on whatever ShipStation plan you're subscribed to there.
Completion checklist
- Shipping is opened from Sales channels → Shipping (`/admin/shipping`), and ShipStation/Shippo show installed before you try to connect an account.
- A Shippo account is connected (test or live token) and at least one carrier account is active.
- A label was bought from a real test order, with a chosen rate and parcel details.
- The order shows a tracking number, is marked fulfilled, and (if opted in) the customer received a shipping email.
- ShipStation's Custom Store connection shows the test order, and a label made there syncs tracking + fulfilled status back to Lulu.
- You've confirmed in your own Shippo/ShipStation dashboard which carriers actually serve your store's origin country.
Troubleshooting
ShipStation or Shippo's page just shows an install card.
That app isn't installed on this store yet. Click “Install ShipStation” or “Install Shippo” on the card — both are free, no payment method needed — and the connect form appears. Shipping labels specifically always need Shippo installed and connected, since there's no platform-wide Shippo account.
"Get rates" returns no rates.
No carrier accounts may be active in your Shippo account yet — activate at least one (USPS/UPS/FedEx/DHL) in the Shippo dashboard, then click "Refresh carriers" on the Shippo settings page and try again. Unusual parcel dimensions or weight can also return zero rates for some carriers.
I'm in Sri Lanka (or another non-US country) — can I use this at all?
You can connect a Shippo or ShipStation account the same as any store, but whether a carrier will actually generate a label from your origin address depends on what Shippo/ShipStation support for that country. Check your Shippo dashboard's carrier accounts for your specific origin before assuming it will work — these services are mainly built around US and major international carriers.
ShipStation never shows my test order.
Double-check the Custom Store URL, username and password were entered in ShipStation exactly as shown on the Lulu page (the password is shown only once — regenerate it if lost), and that ShipStation's Custom Store connection is active, not paused.
A label shows "needs a look before buying again".
Lulu couldn't match that label to a specific Shippo transaction automatically. Check the Shippo dashboard directly for the matching transaction before buying another label for the same order to avoid a duplicate purchase.
Does Lulu take a cut of shipping costs?
No. Lulu charges nothing for Shipping labels, ShipStation, or Shippo. Shippo bills your own Shippo account for postage directly, and ShipStation bills whatever plan you have with them.
Ad Manager: app setup
1. Review the fit
Sell ad space on your storefront: placements, self-serve bookings by customers and marketplace sellers, review, invoices, bank transfer or online payment, and delivery stats. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Ad Manager after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/ad-manager
BlockBuilder Page Builder: app setup
1. Review the fit
Design custom home, product, and landing pages with a visual editor, reusable sections, and mobile-first templates — no code required. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Add a Layout canvas from the theme editor → Apps after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/blockbuilder-page-builder
Built-in Product Reviews: app setup
1. Review the fit
The built-in product reviews every store has, free on every plan: verified-buyer star ratings with a headline and body, a verified-purchase badge, ratings on product cards and in structured data, and moderation with merchant replies from Admin → Reviews. There is nothing to install or pay for here. Paid upgrades are the Judge Product Reviews app in the App Store (Starter $0.99/month, Growth $15/month). This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/judge-product-reviews
BundleCraft Bundles: app setup
1. Review the fit
Merchants group 2–4 products with a percentage off; the storefront bundle section adds all items to the cart and applies the bundle discount through the store’s own discount engine. Managed under Marketing → Bundles. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Bundles after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/bundlecraft-bundles
BuyBar Sticky Add to Cart: app setup
1. Review the fit
When the Add to cart button scrolls out of view, a slim bar slides up from the bottom with the product photo, title, live price, and an Add to cart button — on desktop and mobile. Turn it on per store in the theme editor's Product details settings (Sticky add-to-cart bar). This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Online Store after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/buybar-sticky-add-to-cart
ChatDesk Live Chat & Help: app setup
1. Review the fit
Answer customers in real time with live chat, a shared inbox, saved replies, and a self-serve FAQ page that deflects common questions. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Inbox after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/chatdesk-live-chat
CoinShift Currency Converter: app setup
1. Review the fit
Detect visitor location and display prices in their local currency, add a language switcher, and round converted prices cleanly. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open CoinShift settings after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/coinshift-currency-converter
Drop Shipping: app setup
1. Review the fit
Connect your supplier account (AliExpress, CJdropshipping, Printful, Printify, Zendrop and more), search the catalog from your admin and import products with their variants, images and cost. Your pricing rules set the retail price, stock and supplier cost stay in sync, orders go to the supplier (automatically where the supplier has an order API, otherwise as a ready-to-copy task) and tracking comes back onto the order. You pay the supplier for products and shipping. Needs the Dropshipping module to be switched on for your Lulu installation. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own supplier account (AliExpress, CJ, Printful…). Real, built-in dropshipping — it needs your own supplier account (AliExpress, CJdropshipping, Printful, Printify, Zendrop and others) and the Dropshipping module switched on for this Lulu installation. Once connected: search the supplier catalog from your admin and import products with variants, images and cost; pricing rules set the retail price; stock and supplier cost refresh on a schedule; orders are sent to the supplier (automatically where the supplier has an order API, otherwise as a ready-to-copy task) and tracking numbers come back onto the right order. Reports estimate margin and profit by order, product, supplier and category, and on Enterprise across the stores in your store group and by staff member. Your plan’s synced-product limit (Launch 250, Growth 2,500, Scale 10,000, Enterprise 50,000 active synced products) is shown on the Dropshipping page and enforced when you import or un-archive a product; products you already have keep syncing even if you are over it.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/drop-shipping
Facebook & Instagram: app setup
1. Review the fit
Free sales channel made by Lulu. Lulu publishes a standards-based Meta catalog feed of your products (id, title, description, price, availability, images, link) at a public URL. You add that URL once in Meta Commerce Manager as a scheduled data source, and Meta refetches it on its own schedule so your Facebook Shop and Instagram product tags stay current. The channel page walks you through the Commerce Manager connection, shows how many products are feed-ready and why the rest are not, and keeps your Meta Business, Catalog and Pixel IDs for reference. What it does not do: there is no automatic Meta API sync, no on-Facebook checkout and no pixel injection - those need Meta app review and access tokens. You need your own Meta Commerce Manager account. Lulu charges nothing for this channel. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own Meta Commerce Manager account. Real, built-in Meta catalog feed — it needs your own Meta Commerce Manager account to show anything on Facebook or Instagram. Lulu publishes a standards-based catalog feed of your products (id, title, description, price, availability, images, link) at a public URL; you add that URL once in Commerce Manager as a scheduled data source and Meta refetches it on its own schedule. The channel page walks you through the connection, shows how many products are feed-ready and why the rest are not, and keeps your Meta Business, Catalog and Pixel IDs for reference. Not built: automatic Meta API sync, on-Facebook checkout and pixel injection — those need Meta app review and access tokens. Lulu charges nothing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/facebook-instagram-channel
For You: app setup
1. Review the fit
Remembers which products a shopper has looked at and shows product rows built from that and from your sales: Recently viewed, Similar products, Frequently bought together, Best sellers, New arrivals, Trending and Featured products. Rows can appear on the home page, product pages and the cart, and each one can be switched on or off, renamed and limited to 4–24 products on the For You admin page (a row you place yourself in the theme editor shows its own number of products). Views are stored on our servers only when the shopper has accepted analytics cookies; without consent the Recently viewed list stays on their own device. Frequently bought together needs order history and is refreshed every 6 hours. Featured products is a list you pick yourself. Only products that are active and published to the shopper’s channel are ever shown. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open For You settings after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/foryou-recommendations
Google & YouTube: app setup
1. Review the fit
Free sales channel made by Lulu. Lulu publishes a standards-based Google Merchant Center product feed (g:id, g:title, g:price, g:availability, images, link) at a public URL. You add it once in Merchant Center as a scheduled fetch, and Google refetches it, powering free product listings, Shopping and YouTube product surfaces. The channel page walks you through the Merchant Center connection, shows how many products are feed-ready and why the rest are not, and keeps your Merchant Center ID for reference. What it does not do: there is no Content API sync and no Google-hosted checkout. You need your own Google Merchant Center account. Lulu charges nothing for this channel. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own Google Merchant Center account. Real, built-in Google Merchant Center feed — it needs your own Merchant Center account to show anything on Google or YouTube. Lulu publishes a standards-based product feed (g:id, g:title, g:price, g:availability, images, link) at a public URL; you add it once in Merchant Center as a scheduled fetch and Google refetches it, powering free listings, Shopping and YouTube product surfaces. The channel page walks you through the connection, shows feed readiness and keeps your Merchant Center ID for reference. Not built: Content API sync and Google-hosted checkout. Lulu charges nothing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/google-youtube-channel
Google Customer Reviews: app setup
1. Review the fit
Shows Google's official post-purchase opt-in survey on the order confirmation page, feeding your Google seller rating. Connect your Merchant Center account from Admin -> Google Customer Reviews and paste your Merchant ID -- the Pro plan adds the Google seller-rating badge on every storefront page, plus badge position, survey style and delivery-estimate settings. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own Google Merchant Center account. Real, built-in Google Customer Reviews — it needs your own Google Merchant Center account to do anything. Once connected: sign up for Google Customer Reviews in Merchant Center → Growth → Manage programs, accept the agreement, and paste your Merchant ID into Admin → Google Customer Reviews. The post-purchase opt-in survey then shows on the order confirmation page automatically; the Pro plan adds the Google seller-rating badge on every storefront page. What needs the provider: a Google Merchant Center account and Merchant ID.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/google-customer-reviews
Google Reviews: app setup
1. Review the fit
Pulls your business’s star rating, review count and up to 5 reviews straight from Google (the public Places API’s own cap) and shows them in a carousel, grid or list you place with the theme editor’s App block. Search for your business from Admin → Google Reviews and pick it. On the free Starter plan you sync by hand with Refresh now; Growth ($5.99/month) and Pro ($12.99/month) sync automatically once a day and add a keyword filter that hides negative reviews containing words you choose. A minimum-star filter works on every plan. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires a Google Places API key (your own, or the platform default your operator may have set up). Real, built-in Google Reviews — it needs a Google Places API key to fetch anything. Once a key is available (your own, added in Admin → Google Reviews, or the platform default your operator may have set up): search for your business, pick it, and your rating, review count and reviews sync — on demand with Refresh now on Starter, automatically every day on Growth and Pro. Each sync returns up to 5 reviews (the public Places API’s own cap); Lulu keeps them across syncs, so up to 10 different reviews show (QA doc 1 BUG 015). Add the “App block” section to a template and choose Google Reviews → reviews-widget to show it. What needs the key: nothing renders until one resolves, your own or the platform’s.
- Enable in the theme editor. Open Google Reviews after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/google-reviews
Hammer Auctions & Offers: app setup
1. Review the fit
Put a product under the hammer. Set a starting bid, a closing time and how much each bid must go up by (a fixed amount, a percentage, or a tiered ladder), then add a reserve or a buy-it-now price if you want one. Shoppers bid from the product page or the /auctions index; with proxy bidding on they set a hidden maximum and the server bids for them, second-price, so the board only moves as far as it has to. A bid in the last two minutes extends the clock. When the lot closes the winner is chosen automatically, gets a payment deadline and a reminder before it, and their won line is priced at the hammer price through your normal checkout — no discount codes, no draft orders, no hidden variants, and the stock is held for them while they pay. If they don’t pay, the lot passes to the next highest bidder or comes back for relisting. Make-an-offer runs alongside it with auto-accept, auto-decline and auto-counter rules. Live auctions with a human auctioneer, buyer’s premium and outbound webhooks are NOT included. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Auctions after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/hammer-auctions
Judge Product Reviews: app setup
1. Review the fit
Product reviews with a paid layer when you need more. Installing adds an aggregate fit scale (runs small — true to size — runs large) with your own labels and a fit question on the form, size and colour answers on every review, a rating filter and four sorts, helpful votes, and automatic review-request emails a set number of days after fulfillment. Starter ($0.99/month) and Growth ($15/month) add the features listed on each plan. Uninstalling keeps every review and answer; only the extra features switch off. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Reviews after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/reviews-pro
KeepCart Save for Later: app setup
1. Review the fit
Let shoppers set cart items aside for later This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. undefined
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/keepcart-save-for-later
LoyalLane Rewards: app setup
1. Review the fit
Reward customers with points for orders and referrals, build VIP tiers, and launch a branded rewards page to grow repeat purchases. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Loyalty after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/loyallane-rewards
Lulu POS: app setup
1. Review the fit
Point of Sale for your shop counter: checkout and barcode scanning, printed and email receipts, split payments, saved carts, returns, offline cash sales, daily reports and online-order pickup, all on the stock and customers your online store already uses. Lite is free with your Lulu plan (1 checkout device, 2 cashier accounts). Retail ($29/month) adds exchanges and store credit, staff roles, register hardware and 2 checkout devices with unlimited cashiers; Pro ($59/month) adds branch reports and cross-branch returns with 4 checkout devices. Extra checkout devices are $10/month on Retail and Pro. 0% commission on in-person sales. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/shopwise-pos
Lulu Reserve: app setup
1. Review the fit
Take pre-orders and back-orders, run waitlists with automatic restock emails, and set variant rules, quantity caps and dispatch dates. Reserve runs on the same pre-order engine as Presale Pre-orders (Orders -> Pre-orders), with guided setup. Deposits and partial payments are not offered on Reserve yet. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/reserve-preorders
Marketplace Connect: app setup
1. Review the fit
Made by Lulu. Connect your own Amazon, eBay and Etsy seller accounts and manage them from Sales channels -> Marketplaces: publish products as listings and keep inventory and price in sync, import marketplace orders into your Orders list, and read buyer messages and reply to reviews where the marketplace allows it. On Unlimited sync you also get bulk listing management (publish, unpublish, override the price or set a quantity buffer for many listings at once, with a per-item result you can retry) and cross-region selling (a marketplace currency per channel, priced at a live exchange rate plus your markup and rounding). A marketplace can only be connected once the platform operator has added that marketplace's developer credentials; until then its card says so. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/feedsync-marketplace-channels
MirrorMe Try-On: app setup
1. Review the fit
Shoppers try products on live from their camera or a photo — face-landmark AR that runs entirely in the browser: no images are ever uploaded or stored. Enable per product with an anchor (eyes, ears) and overlay image. Apparel photo try-on is coming and will require an external provider. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Products after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/mirrorme-tryon
Payment Gateway Connectors: app setup
1. Review the fit
Accept cash on delivery, bank transfer, Stripe cards, PayPal and the Sri Lankan gateways PayHere, WEBXPAY, Payable, Onepay (cards and LankaQR), Mintpay and Koko. Payment status comes back to the order automatically. Each gateway uses your own merchant account. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/payment-gateways
Postbox Email & SMS: app setup
1. Review the fit
Send email campaigns from 250+ built-in templates, capture signups with embeddable popups and forms, and put welcome, abandoned-checkout, post-purchase and win-back flows on autopilot — with built-in AI to draft subject lines and copy. Standard adds AI-written form copy and removes the platform footer; Pro adds open/click/revenue reporting, per-recipient product recommendations, and dynamic content personalized by segment, tag or country. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/postbox-email-marketing
Presale Pre-orders: app setup
1. Review the fit
Sell what you haven’t got yet. Build a pre-order campaign (pick the products, decide whether Pre-order shows only when stock runs out or always, set the expected ship date or leave it to be finalised), and every covered product gets a Pre-order button, a ship-date note and a badge on its card. Choose how much is charged at checkout: the full amount, a deposit with the rest due on a date or when you fulfil, or nothing now. Unit caps and per-customer limits are enforced at checkout, not just in the widget. Orders are held from fulfillment until the ship date and released automatically, and shoppers get balance reminders, delay notices and a “ready to ship” email. Charging a saved card automatically is NOT included — Lulu has no card vaulting, so the balance goes out as a payment request with a pay-balance link the shopper pays through your normal checkout. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Pre-orders after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/presale-preorders
PrintCraft Design Studio: app setup
1. Review the fit
A product customiser for print-on-demand catalogues. Shoppers add text layers, upload their own artwork, place it inside a bounded print area on the front and back, and pick a colour and size before adding the finished design to the cart. Every design is captured with the order so you can reproduce it. Install, then switch on the Customize button in the theme editor; uninstalling hides the studio but keeps every design on its order. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Configure in the theme editor after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/printcraft-design-studio
QuickPeek Quick View: app setup
1. Review the fit
Shoppers hover any product card and open a quick-view pop-up with the gallery, size options, stock and add to cart — no page change. One switch in the theme editor turns it on for every card. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Configure in the theme editor after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/quickpeek-quick-view
Recur Subscriptions: app setup
1. Review the fit
Selling plans with percentage discounts, a Subscribe & save picker on product pages, and a recurring engine that creates an order automatically each cycle — cash on delivery, or charged to the subscriber’s saved card. Shoppers pause, resume or cancel from their account. Automatic card charging is available on stores that take cards with their own Stripe account and have saved cards switched on; everywhere else each order stays cash on delivery. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires a payment provider that supports stored cards. Real, built-in recurring orders — collected cash on delivery, or charged automatically to the subscriber’s saved card where your store takes cards with its own Stripe account. Build subscribe-and-save plans in Products → Subscriptions (any cadence in days, weeks, or months, a percentage off, offered on every product or just the ones you pick), then add the “App block” section to your product template and choose Recur Subscriptions → plan-picker. Each cycle creates a real order in Orders, unpaid until you collect, and customers pause, resume, or cancel themselves from their account page, or swap to another product or option the plan covers (re-priced at the plan price, less an optional swap discount you set). You choose whether subscribers keep their price when you re-price a product or follow the current price: a decrease applies from the next order, an increase is emailed first and applies only after the notice period you set (7-60 days). Your apps and integrations can list, pause, resume and cancel subscriptions through the Admin API (read_subscriptions / write_subscriptions scopes, Settings → Apps and sales channels → Develop apps), and signed webhooks for new, changed and cancelled subscriptions and for each successful or failed order cycle are in Settings → Notifications → Webhooks. Automatic card charging: on a store whose Stripe card payments use its own Stripe account with saved cards turned on, switch on “Charge the saved card automatically” in Products → Subscriptions → Payments. Signed-in subscribers with a verified email can then choose to pay each delivery with a saved card and give their permission for it; each order is charged its full total when it is placed. If a charge fails the order stays open to collect on delivery, the customer gets one email to pay or change the card, one retry runs three days later, and the subscription is flagged for you. Customers can switch back to pay on delivery or change the card from their account. Everywhere else (no Stripe, the platform’s shared Stripe key, or a provider that can’t store cards) every order is cash on delivery.
- Enable in the theme editor. Open Subscriptions after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/recur-subscriptions
Sales Channel & Tracking Integration: app setup
1. Review the fit
Track visits with Google Analytics 4 and share your catalog with Google Merchant Center and the Meta (Facebook and Instagram) catalog through automatic product feeds. Meta Pixel, Conversions API and TikTok Pixel are coming next. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires an external service. Google Analytics 4 page tracking on your storefront (add your measurement ID), GA reports in Analytics, and product feeds for Google Merchant Center and the Meta (Facebook and Instagram) catalog that Google and Meta refresh on their own schedule. Not built yet: the Meta Pixel (the ID is saved but not placed on the storefront), the Meta Conversions API, the TikTok Pixel, GA4 purchase and add-to-cart events, and push-style feed sync.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/sales-channels-tracking
ShareBag Cart Sharing: app setup
1. Review the fit
Adds a “Share Bag” button to the cart that copies a public link to the shopper’s current bag. Anyone opening the link sees the items at live prices and can add the whole bag to their own cart in one tap. Custom-designed items stay private. Toggle it in the theme editor’s cart settings. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open cart activity dashboard after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/sharebag-cart-share
Shipping & Delivery: app setup
1. Review the fit
Set shipping zones by country, city or postal code, flat rates with a minimum order value, free shipping offers, local delivery and cash on delivery. Add tracking numbers with carrier links and let tracking updates mark orders delivered. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/shipping-delivery
Shippo: app setup
1. Review the fit
Free app made by Lulu. Connect your own Shippo account by pasting your Shippo API token - a free test token works end to end, so you can rehearse the whole flow before you spend anything. Once connected, the carrier accounts on your Shippo account are imported, and from any order you can compare live rates, buy, print and void labels: the label PDF is kept with the order behind your admin login, the fulfillment, tracking number and tracking link are created for you, and Shippo tracking webhooks keep the order moving to Delivered. The Shipping labels list and the label card on the order page stay built into Lulu; they buy through the Shippo account you connect here. Carriers are the ones Shippo supports on your account (mostly US and international carriers) - a Sri Lankan store can connect, but buying a label depends on a carrier serving your ship-from country. You pay Shippo for postage; Lulu adds no markup and takes no cut. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own Shippo account (a free test token works). Real, built-in label buying — it needs your own Shippo account to do anything. Once connected: open an order, pick the box and weight, compare live rates across the carriers on your Shippo account, buy, and the label PDF is stored with the order behind your admin login while the fulfillment, tracking number and tracking link are created for you. Void an unused label for a refund; Shippo’s tracking webhooks keep the order moving to Delivered. The ship-from address comes from a real location in Settings → Locations, never free text. What needs the provider: a Shippo API token — their free TEST token works end to end, so you can rehearse the whole flow before spending anything. You pay Shippo for postage; Lulu adds no markup. Shippo Connect managed accounts and platform-billed postage are not built (they need a Shippo platform agreement).
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/shippo-labels
ShipStation: app setup
1. Review the fit
Free app made by Lulu. Connect the ShipStation account you already ship from: Lulu gives you a Custom Store URL with its own username and password; you paste them into ShipStation once, and ShipStation pulls your paid, unfulfilled orders on its own schedule - line items, quantities, the shipping address, the service the shopper chose. When you ship in ShipStation, it posts the tracking number back: the order is fulfilled here, the carrier and tracking link are recorded, inventory moves, and the shipping-confirmation email goes out. Choose which order statuses ShipStation sees, how far back the export looks, and whether the customer is notified. An optional API mode (your ShipStation key and secret) pushes orders instead of waiting to be polled. Carriers are the ones on your ShipStation account (mostly US and international carriers). You pay ShipStation for your plan and your carriers for postage; Lulu charges nothing. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own ShipStation account. Real, built-in ShipStation integration — it needs your own ShipStation account to do anything. Once connected: Lulu gives you a Custom Store URL with its own username and password, ShipStation pulls your paid, unfulfilled orders on its schedule, and the tracking number it posts back creates the fulfillment here, records the carrier and a working tracking link, moves inventory and sends the shipping email. You choose which order statuses it sees, how far back the export looks and whether the customer is notified, and every pull and shipment notice is in the activity log. An optional API mode (your ShipStation key and secret) pushes orders instead of waiting to be polled. What needs the provider: a ShipStation plan and your carrier accounts — Lulu charges nothing and never touches your ShipStation billing. Buying labels inside Lulu is a different app (Shippo), and Lulu is not listed in the ShipStation Marketplace — the Custom Store contract is how it connects.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/shipstation-connect
SideBySide Compare: app setup
1. Review the fit
Let shoppers compare up to 4 products side by side: merchant-curated attribute rows built on your metafields, a differences-only toggle, sticky first column, and full keyboard/screen-reader support. Configure attributes in Admin → Products → Compare, then place the Compare grid app block in the theme editor. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Compare after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/sidebyside-compare
SizeFit Size Guide: app setup
1. Review the fit
Adds a "Size guide" link beside the Size option on product pages. Upload a chart image or build a measurements table; the pop-up only appears on products that actually have sizes. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open size charts after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/sizefit-size-guide
Storyline Product Content: app setup
1. Review the fit
Give every product a story page: rich text, image galleries, spec tables, FAQs, quotes, callouts and video embeds — assembled as blocks in the product editor and rendered through an app block you place in the theme editor. Draft/publish workflow, sanitized content, FAQ and Article structured data built in. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Products after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/storyline-product-content
UpCart Upsell & Cross-Sell: app setup
1. Review the fit
Cross-sell on every product page: a “See similar styles” thumbnail row with a Shop Similar pop-up (hand-pick the products in Admin → Products → Similar products, or let automatic recommendations fill the row), plus “Bundle & save” cards with one-click add for any active bundle that includes the product. Switch both blocks on in the theme editor’s Product details settings. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open UpCart settings after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/upcart-upsell-cross-sell
WhatsApp Sales & Recovery: app setup
1. Review the fit
Connect your WhatsApp Business number, send invoices to customers on WhatsApp and let customers opt in to WhatsApp updates. Chat button, order confirmations, abandoned-cart recovery and shipping updates on WhatsApp are coming next. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires an external service. Connect your own WhatsApp Business (Cloud API) number in Settings → Notifications and send draft-order invoices to customers on WhatsApp; customers can opt in to WhatsApp marketing from their account, and your WhatsApp link shows in the store footer. Not built yet: a floating WhatsApp chat button, WhatsApp order confirmations, abandoned-cart recovery and shipping updates on WhatsApp (these go by email today), product enquiries, and the ChatWise integration.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/whatsapp-sales
WiseSEO: app setup
1. Review the fit
Get found on search engines and in AI answers. WiseSEO checks every product as you write it (a focus keyphrase, 12 SEO checks, 7 readability checks and a search-result snippet preview with pixel-width gauges) and adds a store-wide SEO health dashboard, complete schema.org structured data (Product, Organization, WebSite, breadcrumbs, FAQ, articles) and per-store sitemaps. For AI search, also called generative engine optimisation (GEO), the SEO & AI panel turns search-engine indexing on or off and lets you allow or block each AI crawler, grouped by model training versus live answer retrieval, with live robots.txt and llms.txt previews. New stores stay invisible to crawlers until you switch indexing on. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/searchboost-seo
Wishlist Plus: app setup
1. Review the fit
Upgrades the built-in wishlist to a multi-list board: shoppers create named lists, pick the list (and size) straight from the heart on any product card, share a list by link, and see recently viewed products under the board. Uninstalling keeps every saved item; the storefront falls back to the single built-in list. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Enable in the theme editor. Open Wishlist Plus after installing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/wishlist-plus
WishWell Wishlist: app setup
1. Review the fit
The built-in wishlist every store has: shoppers save favourites with the heart icon and find them on the store’s Wishlist page. Multiple named lists, sharing and the heart picker are in Wishlist Plus. This app has available functionality. Check the live listing for the features supported by each plan.
2. Check requirements
Check these requirements before installing.
- Review your store, theme, and connected-service requirements in the current listing.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/wishwell-wishlist
Zendrop Dropshipping: app setup
1. Review the fit
Source products from Zendrop and sell them in your store. Sign in to Zendrop once, browse the catalog from your admin, and import a product with its variants, images, cost and shipping estimate — your pricing rules set the retail price. Inventory and cost are refreshed on a schedule, and tracking numbers come back automatically onto the right order, with the shipping email sent for you. ONE thing is honest and unavoidable: Zendrop has no order-creation API, so Lulu cannot place your orders for you. When an order needs Zendrop, it appears as a task with the shopper’s address and the exact lines to order, ready to copy; you place it in Zendrop, paste the Zendrop order id back, and tracking then flows in on its own. If Zendrop ever opens an order API, the automatic path is already built behind a capability flag. Needs the Dropshipping module to be switched on for your Lulu installation. You pay Zendrop for products and shipping; Lulu charges nothing. Some functionality is available, while other capabilities may still be planned. Review the live listing before relying on a particular workflow.
2. Check requirements
Check these requirements before installing.
- Requires your own Zendrop account. Real, built-in Zendrop sourcing — it needs your own Zendrop account, and the Dropshipping module switched on for this Lulu installation. Once connected: browse the Zendrop catalog from your admin and import a product with its variants, images, cost and shipping estimate (your pricing rules set the retail price), stock and cost refresh every 6 hours, and tracking numbers come back onto the right order with the shipping email sent for you. One limit is the provider’s, not ours: Zendrop has NO order-creation API, so Lulu cannot place your orders. An order that needs Zendrop becomes a task with the shopper’s address and the exact lines to copy; you place it in Zendrop, record the Zendrop order id, and tracking flows in from there. Automatic placement is already built behind a capability flag for the day Zendrop opens an API.
3. Choose and install
Sign in to the store where you want to use the app. Review its requested access and choose a plan that fits your usage. Paid plans and provider charges are separate from your store package.
4. Configure and preview
Open the app from your admin and complete its setup. If it adds a storefront component, enable the appropriate app block or section in your theme. Preview on desktop and mobile before publishing.
5. Test the customer journey
Use sample products or a test order to check the result. Review app usage and plan limits before increasing traffic. Contact the app’s support team through the listing if the result differs from what you expected.
Illustrated guide: lulu.us.com/help/apps/zendrop-dropshipping