Get Started

Introduction

An infinite AI team that builds and runs your commerce business end-to-end.

Most stores are a patchwork of a platform, a theme, a developer and a dozen apps, all run by hand. Prezense replaces it with one AI team that builds your store and keeps it running.

Describe your business and Prezense builds the storefront, sets up your catalog and turns on the tools that help you sell. Then it handles the daily work, from orders and refunds to campaigns and reporting, while you make the calls that matter.

Platform overview

Prezense covers the full life of a store: building it, selling, daily operations and reporting. Everything is built in, and work is handed off in conversation rather than done by hand. It works for a first store, a move from another platform (see Migrate) or a small team running more with less.

  1. 01Storefront

    Your storefront is designed from a description of your brand, not a template.

    • A custom storefront, refined through conversation
    • A catalog set up from a spreadsheet, a list or your old store
    • Publishing on your own domain, with instant rollback
    Example request

    Build a store for handmade candles with a warm, minimal look.

  2. 02Smart Commerce

    Selling tools that usually come as separate apps, built in.

    • Recommendations, trending products and smart search help shoppers find things
    • Bundles and post-purchase offers raise order value
    • Reviews and loyalty bring customers back
    • Cart recovery and notifications win back lost sales
    • Fraud protection and returns management protect margins
    Example request

    Turn on cart recovery emails and write them in our brand voice.

  3. 03Operations

    Routine work is done by agents, or in the dashboard.

    • Fulfill, refund and cancel orders
    • Buy shipping labels and track deliveries
    • Keep products, prices and stock up to date
    • Create discount codes and send email campaigns
    Example request

    Create a 15% discount code for returning customers, valid until Sunday.

  4. 04Analytics

    Sales, profit and traffic are tracked from launch.

    • See revenue, profit and visitor trends
    • Ask questions and get answers from your own data
    Example request

    Compare last week's sales with the week before.

Getting access

Prezense runs in the browser. Sign in with Google or email. A new store offers to import your catalog first; skip it to start describing your store.

Agent work is measured in credits. See Plans & billing and Credits & usage for pricing.

Core concepts

The few ideas the rest of Prezense is built on.

Stores

Everything belongs to a store, with its own storefront, products, customers, orders and settings. Run several from one account and switch any time; agents and the dashboard work on the one you have selected.

Agents

Agents are who you talk to. They can do anything the dashboard can, build your storefront, and carry out multi-step work, like importing a catalog and writing every description, on their own. See What agents can do.

Chats

You work in chats. Each belongs to one store and is saved, so you can pick up where you left off. Use one chat per task, and pin the ones you return to. See Chats & stores.

Approvals

Before changing anything, agents show an approval card describing what they will do. Nothing happens until you approve, and a declined action isn't retried.

Type of actionExamplesApproval
Looking things upReading orders, products, customers, analytics and settingsNever asks
Routine changesAdding a product, editing an email template, creating a discountAsks first, and can be always allowed for the rest of the chat
Sensitive actionsDeleting data, issuing refunds, buying shipping labelsAsks every time, with no way to skip

See Approvals.

Preview and publishing

Design and page changes happen in a private preview first; shoppers only see what you publish. The previous version is always kept, so you can switch straight back.

Store data is different: products, prices, orders and settings are shared with the live store, so changes to them apply immediately.

The dashboard

The dashboard shows the same store agents work on, for when you'd rather look or make a change yourself. Changes in either place show up in both.

Memory

Agents remember what you tell them, like your brand voice or returns policy, and bring it into every chat. Ask them to remember, recall or forget anything. See Memory.

Example request

Remember that we only ship within the UK and EU.

Credits

Agent work is measured in credits. Quick questions use little; long tasks, stronger models and higher effort use more. See Credits & usage and Models & effort.

Migrate

Overview

Bring your store over from another platform in one go.

Prezense copies your products, customers, order history, collections, discount codes and more from Shopify, WooCommerce, BigCommerce, Wix, Squarespace, Adobe Commerce, Lightspeed E-Series or PrestaShop, or from a CSV file for anywhere else. Your old store is only read, so you can keep selling there until you switch.

Supported platforms

What each platform needs:

PlatformWhat you'll needGood to know
ShopifyYour myshopify.com address and an Admin API access tokenUp to 100 variants per product; order history past 60 days needs the all-orders permission
WooCommerceYour store's web address, plus a consumer key and secretYour site must use HTTPS
BigCommerceYour store hash or API path, and an access token—
WixYour site ID and an API keyStock isn't shared; set it after importing
SquarespaceAn API keyRequires a Squarespace Commerce plan
Adobe Commerce (Magento)Your store's web address and an integration access tokenYour site must use HTTPS
Lightspeed E-Series (Ecwid)Your store ID and a custom app's secret token—
PrestaShopYour store's web address and a webservice keyYour site must use HTTPS
Any other platformA products CSV file, and optionally a customers CSVShopify and WooCommerce exports work as they are; up to 20 MB per file

Creating an access key

A read-only key is all Prezense needs. Anything you leave it without access to is skipped, and the results say so:

  • Shopify. Settings → Apps → Develop apps: create an app with read access to products, customers, orders, all orders, discounts, locations, inventory, online store pages, content and navigation. Install it and copy the Admin API token.
  • WooCommerce. WooCommerce → Settings → Advanced → REST API: add a Read key, copy the key and secret. Published pages and blog posts are read from your site directly.
  • BigCommerce. Settings → Store-level API accounts: create one with Products, Customers, Orders, Marketing, Content, Store Inventory and Sites & Routes read-only, copy the token and API path.
  • Wix. API Keys Manager: create a key with Wix Stores, Wix eCommerce, Contacts, Coupons and Wix Blog permissions. Your site ID follows /dashboard/ in your dashboard's address.
  • Squarespace. Settings → Advanced → Developer API Keys: generate a key with Products, Orders and Profiles read access.
  • Adobe Commerce. System → Extensions → Integrations: add one with Catalog, Customers, Sales, Marketing, Stores and Content, activate it, copy the Access Token.
  • Lightspeed E-Series. Apps → My Apps: create a custom app with read access to the catalog, customers, orders, discount coupons and reviews, copy its secret token. Your store ID is at the bottom of the admin.
  • PrestaShop. Advanced Parameters → Webservice: turn it on and add a key with GET on products, combinations, product options and values, stock, categories, customers, addresses, orders, cart rules and CMS.

How a migration works

Four stages. Nothing is added until you choose to import.

  1. 01Connect your old store

    In Settings → Import data, pick your platform and enter its details. New stores offer this as their first step.

    • Read-only, so your old store is never changed
    • Your key is used once and never saved
  2. 02Let Prezense analyse it

    Prezense reads and checks every product, mapping it onto Prezense and fixing problems automatically where it can, then reads your customers, orders and everything else your platform offers.

    • Progress is shown as it works
    • Live products stay live, drafts stay drafts, and anything unclear arrives as a draft
  3. 03Review the results

    See how many products and variants are ready, how many customers, orders, collections and so on were found, plus any notes.

    • Products that couldn't be fixed are listed with the reason and skipped
    • Notes flag anything that won't fully carry over, and anything your key wasn't allowed to read
  4. 04Import

    Products come in first, then customers, order history, collections, discount codes and the rest, in the background.

    • Resume an interrupted import without duplicates
    • Run a new import any time

Using agents

Once a store is analysed, agents can report progress and run the import, with your approval. Connecting happens on the Import data page, so keys never go into a chat.

Example request

Is my Shopify import ready? How many customers and orders did it find? If it looks right, go ahead and import it.

Before you start

  • Up to 5,000 products per import.
  • Add an inventory location first to bring stock levels over, unless your old platform has locations of its own (they come with it).
  • Analysis uses a few credits. See Credits & usage.
  • Up to 25,000 of each kind (customers, orders, …); past that, the newest come over.
  • What comes over depends on your platform. Your design, apps and subscriptions stay behind. See What gets migrated.

What gets migrated

Your products, and whatever else your old platform shares.

Every platform brings its products, and every connected platform its redirects. The rest depends on what each platform lets other software read. The Import data page says what will come over before you connect.

PlatformCustomersOrdersCollectionsDiscount codesReviewsStock per locationPages & blogGift cards
ShopifyYesYesYesYes—YesYes—
WooCommerceYesYesYesYesYes—Yes—
BigCommerceYesYesYesYesYesYesYesYes
WixYesYesYesYes——Blog only—
SquarespaceYesYesYes—————
Adobe CommerceYesYesYesYes—YesPages only—
Lightspeed E-SeriesYesYesYesYesYes———
PrestaShopYesYesYesYes——Pages only—
CSV fileYes———————

What each part brings

  • Products. Variants, prices, images, stock, tags and SKUs, plus each product's SEO title and description and its extra details (materials, care, …), which become additional details.
  • Customers. Names, emails, addresses, tags and notes, as shopper accounts. They sign in with an emailed code, so no passwords move. Anyone who already has an account in your store keeps theirs. Only customers who agreed to marketing on your old store join your email list.
  • Order history. Every order with its items, totals, tax, shipping, discounts, refunds and tracking, linked to the customer and the products. It's a record only: nobody is charged or emailed, stock doesn't move, and reorder reminders and loyalty tiers ignore it. Orders still open on your old store arrive unfulfilled, since they may still need shipping.
  • Collections. Each collection or category with its products, in order, and its image and SEO details.
  • Discount codes. Percentage and amount-off codes, with their minimum spend, usage counts and dates. A code that only applied to some products arrives switched off, so you can check it before turning it on. Free-shipping and buy-X-get-Y codes don't carry over; recreate them on the Promotions page.
  • Reviews. Published reviews, with their rating, text and reviewer, on the products they were for.
  • Stock per location. Each location becomes one of yours (or matches one with the same name), with its stock counts.
  • Pages and blog posts. Their text, images and SEO details. Drafts arrive as drafts.
  • Gift card balances. Cards with money left on them, with their balance and expiry. Codes are stored scrambled, so not even Prezense can read them back; customers keep using the code they have.
  • Redirects. Every old product, collection and page address points at its new one, plus any redirects you'd set up on your old store, so links and search rankings keep working.

What stays behind

  • Your design and theme. Your storefront is built fresh in Prezense.
  • Apps and their data, apart from what's listed above.
  • Subscriptions. They're tied to your old payment provider and can't move safely.
  • Passwords. Customers sign in with an emailed code instead.
  • Order history from a CSV file. Order exports differ too much between platforms to read reliably; connect your platform directly if it's listed.

Prices, tax and shipping settings are set up in Prezense rather than copied; see Operations.

After you migrate

A few checks before you switch over.

  • Read the notes. The Import data page lists anything that didn't fully carry over and why — a permission your key didn't have, codes that need recreating, products that needed a look.
  • Check switched-off discount codes. Codes that only applied to some products arrive switched off on the Promotions page. Check each before turning it on.
  • Ship open orders. Orders that were still open on your old store arrive unfulfilled on the Orders page. Fulfil them here, or on your old store before you switch — not both.
  • Look over your customers. Imported customers appear on the Customers page, including those who never ordered. They can sign in to your store with their email.
  • Point your domain at Prezense. Once you're happy, connect your domain. Old links then land on the right pages through the imported redirects.

Imports never change your old store, and running one again only adds what's new, so you can import again just before you switch to catch the latest orders and customers.