Vendzi

For online stores

A storefront, a feed, and the content that feeds it.

Products and stock on one side; pages, guides and structured data on the other. Most stores bolt a blog onto a shop — here the catalogue and the content are the same system, on the same domain.

Enterprise-grade ecommerce, not a checkout plugin

Your own site on your own domain

Your first campaign is built from your catalogue

Today’s orders

Live record

  1. 09:14

    New order · 2 items · Coupon applied

    Checkout · Client attached

  2. 10:02

    Catalog with variants

    Stock and availability per product

  3. 11:30

    Journal · Routine guide

    Same domain that sells the product

Illustrative sample — your catalog, content and campaigns.

The daily friction

What actually goes wrong running online stores

  1. The shop and the content live apart

    A store on one platform and a blog on another. Two domains competing for the same search terms, and no link between an article and the product it sells.

  2. A checkout that loses orders

    A cart that empties on a phone, a coupon that applies twice, and no way to send the customer a payment link instead.

  3. The feed breaks silently

    Merchant Center disapproves listings because a price or an availability flag drifted, and nothing tells you until the traffic is already gone.

  4. Every change needs a developer

    A landing page, a size guide, a new collection — each one a ticket, a sprint and a deploy.

How Vendzi handles it

The same problems, solved on one system

Everything below is in the product today — not a roadmap item.

Catalogue with real structure

Products, categories and variants with SKUs, barcodes and per-variant stock — the shape a feed and a filter both need.

Checkout with server authority

Amounts are computed on the server, never taken from the browser, and every payment execution is duplicate-protected.

Pages, guides and structured data

A block editor and a blog on the same domain, with sitemap, canonical URLs and JSON-LD generated for you.

A feed built from the catalogue

Google category per product, and a feed generator that emits what Merchant Center asks for rather than a hand-maintained spreadsheet.

Campaigns generated, then edited

A full search campaign built out of your catalogue — ad groups, headlines, descriptions, sitelinks and keywords — ready for you to adjust.

One client record per customer

Orders, contact details and history on one record, so a returning customer is recognised instead of re-created at checkout.

A week on Vendzi

From first read to second order

One record follows the customer from the article to the reorder — nothing lives in a spreadsheet.

  1. Discover

    Found through content

    Routine guides and journal posts live on the same domain that sells the product, with sitemap and structured data handled.

  2. Shop

    Variants that read clearly

    Size, shade and refill sit under one product, each with its own stock and availability.

  3. Checkout

    Discounts without drama

    Coupons, order history and a real checkout. Amounts are set on the server and every execution is duplicate-protected.

  4. Amplify

    Feed and ads in one place

    The product feed Google Shopping expects, and Google Ads managed next to the orders those ads produced.

  5. Return

    The second order on record

    Every order lands on the client record, and a payment link recovers the checkout that almost got away.

The parts you will live in

The parts of the platform online stores use most

Same subscription underneath. These are the rooms you will spend the day in.

Enterprise-grade ecommerce, not a checkout plugin

Commerce

A real catalogue with variants, SKUs and per-variant stock; fulfilment as shipping, pickup, digital or service; and one order table that the storefront, the counter and the back office all write to.

  • Variants with tenant-unique SKUs and barcodes, priced as an adjustment on the product
  • Stock per variant with its own status, plus a reorder point per product
  • Retail and wholesale prices held on the same product
  • Fulfilment as shipping, pickup, digital or service, with tracking attached

Your own site on your own domain

Website, content & SEO

Start from the AI builder or the block editor — either way you get service and product pages generated from your catalogue, published instantly and indexed properly.

  • Block-based page editor — no deploy to change content
  • The AI builder drafts the first version from a short conversation
  • Service and product pages generated from your catalog
  • Blog for guides and announcements, published in a click

Your first campaign is built from your catalogue

Advertising & growth

Vendzi generates a complete search campaign — ad groups, headlines, descriptions, sitelinks, callouts and keywords — out of the products and services you already sell, then hands it to you to edit. No blank page, and nothing invented to fill a gap.

  • Search campaigns generated from your catalogue and grouped by category
  • Headlines and descriptions assembled from your own titles, prices and city
  • Keywords taken from catalogue titles that actually exist
  • Any asset it cannot build is reported by name, with the reason, instead of guessed

Your account, your money

Payments

Connect the payment provider you already use. Money settles to you; the platform never holds it.

  • Per-shop provider connections with credentials stored server-side
  • Card payments and PayPal, connected through each provider’s own onboarding
  • Payment links sent by email, SMS or WhatsApp
  • Amounts are authoritative on the server — the browser cannot set a price

Questions

Questions we get from online stores

If yours is not here, ask when you sign up — you will get a person.

Do I need to take bookings to use Vendzi?

No. Booking is a module you can leave off entirely. A pure online store runs the catalogue, cart, checkout, stock, fulfilment and feed without a calendar.

Can I keep my domain and my rankings?

Point your domain at the shop and keep old addresses as aliases, so existing links and indexed URLs keep resolving while the new site takes over.

How does the Google Shopping feed stay correct?

It is generated from the live catalogue rather than maintained by hand, so a price or stock change is reflected the next time the feed is produced.

Same platform

Also built for

Same platform underneath. What changes is which parts carry the weight — and nothing is locked in.

Begin

Ready to put the catalogue and the content on one domain?

Create your shop, add your services and hours, and start taking bookings today.

No developer needed · Connect the payment provider you already use