Skip to content

Grovv for eCommerceFrom the supplier's invoice to a product on your site

Workflow automation for stores that run the business in Caspit and sell on WooCommerce. I built it for campro.co.il, an outdoor and camping gear store: a supplier invoice comes in, AI reads it, the SKUs and stock are opened in Caspit, and the product goes up on the site with its description, images and SEO. Orders from the site flow back to Caspit, and stock stays in sync.

  1. Supplier invoice
  2. Caspit
  3. WooCommerce
  4. The customer

One invoice, from the supplier to the shelf on your site

What used to be typed by hand into two systems now happens once. You approve, the system does the work.

Illustrative: the items, SKUs and quantities are examples.

What it looks like from the inside

Two screens from the system: the catalogue with stock from Caspit, and the publishing screen where AI fills in and you approve.

Stock, straight from Caspit

One click on "Load from Caspit" brings current stock into the catalogue. Every item is marked: in stock, low stock or sold out.

Illustrative: the items, prices and quantities are examples.

The publishing screen: AI fills in, you approve

You click "Create AI content" and the system goes through the product part by part. In each part its suggestions are waiting, each with its source, and you decide which to use.

Illustrative: a recreation of the publishing screen, with an example product and data.

Purchasing and sales talk to the same Caspit

Caspit stays the source of truth. Suppliers, the site and orders connect to it, not the other way round.

Facing suppliers

Supplier catalogue
Every supplier's catalogue sits in one place, filtered by supplier and by status: what is already on the site, and what is not yet.
Supplier orders
Purchase orders to suppliers are built from the catalogue and managed in the same system that later takes in the invoice.

Facing customers

A purchase on the site reaches Caspit
An order a customer places on the site is recorded in Caspit through the interface, without typing it again.
Stock updated through the interface
Stock on the site is updated from Caspit through the interface, so the site shows what is on the shelf.

The catalogue on the site is managed, not just uploaded

Once the product is on the site, people have to find it. Tags, categories and SEO are managed from the same screen.

  • Tag management

    The system proposes tags in three groups: existing ones that fit the product, new ones waiting for approval, and rejected ones. A new tag that is too close to an existing one is rejected as a likely typo.

  • Category management

    An item's category in Caspit sets its category on the site, and one column in the catalogue shows what each item is still missing: an image or a category.

  • SEO management

    Every product has nine SEO fields, among them the title, meta description, URL, keyword and image description, with a score that shows what is still missing.

  • SEO AI

    AI writes the descriptions, the keyword and the SEO fields from the product's verified data. The keyword includes the model, so similar products do not compete for the same phrase.

Illustrative: the tags, categories and phrases are examples.

AI proposes. You approve.

The automation saves the typing, not the judgment. These are the rules the system does not break.

  • Caspit is the source of truth

    Name, SKU, barcodes, price, colour and size are read from Caspit. The system never invents a value that is not there.

  • The price stays yours

    AI does not touch the price fields. A product with no retail price is not published.

  • Verified beats guessed

    An attribute that was not verified against a real source stays blank. No guessed weight, material or size.

  • No widened claims

    If the manufacturer gives a five-year warranty on seams and zippers, that is what the site says, not "a five-year warranty".

  • No duplicates

    A product is identified by SKU and barcode: a new one is created, an existing one is updated.

  • A check before publishing

    Before saving, the facts, the SEO, the images and the colours are checked, and only then does the product go up.

Built for campro.co.il

I built the system for campro, an outdoor and camping gear store, together with the site's theme. It was built around the store's own process: from the invoice that arrives from the supplier to the order that goes out to the customer.

  • WooCommerce
  • Caspit
  • Cloudflare
CAMPROVisit campro.co.il

Running a store on Caspit and WooCommerce?

Tell me how a supplier invoice becomes a product on your site today. I'll tell you what can be automated, and in what order.