In beta with first customers. Out of beta and taking new customers from 26 October. Talk to us

Solutions · By process

Supplier price lists in any layout, checked before they touch your prices.

A webshop can buy from hundreds of vendors, each sending prices in its own spreadsheet that changes again next quarter. StencilFlow finds the table and the columns by pattern recognition, a person confirms the mapping once, and the vendor's naming is remembered. New prices are calculated from your discount, margin and rounding tables and delivered as a file for upload.

What lands in the inbox

  • Excel price list
  • CSV export
  • Multi-sheet workbooks

Read, checked against your data and handed off, with people deciding the exceptions.

The flow

From inbox to system, step by step

Every case follows the same visible path. Where a rule cannot decide, a person does.

  1. Mailbox
  2. Find table
  3. Confirm mapping
  4. Match products
  5. Calculate prices
  6. Upload file

Step by step

How it runs, step by step

A worked example with made-up names. Rules do the checking; people decide what the rules cannot.

  1. 1

    Every vendor, its own spreadsheet

    A webshop can buy from hundreds of vendors, each with a different layout that changes again.

  2. 2

    Forward it in

    Vendor files go to one tagged mailbox. Only allowed senders are admitted.

  3. 3

    Find the table

    The engine reads layout and column meaning, not a fixed template: header row, names in several languages, and the values themselves.

  4. 4

    One screen, one confirm

    A person sees the proposed mapping with sample values, flagged rows first, and confirms.

  5. 5

    Remembered for next time

    Confirmed headers are stored per vendor. The next file from them maps itself; only new things are asked.

  6. 6

    Compare with what is live

    The shop's daily product export is the reference: each vendor row is matched by EAN, then SKU.

  7. 7

    Rules before prices

    Tables your purchasing team owns drive the price. A missing rule is never defaulted.

  8. 8

    Calculate the new price

    Vendor discount, then brand margin for the price band, then rounding. Example with made-up numbers.

  9. 9

    Only what changed, ready to upload

    A person uploads the file; nothing is pushed live silently.

Before and after

Supplier price lists, with and without StencilFlow

Today

  • Copy-paste from dozens or hundreds of vendors' sheets into your own
  • Layout changes break macros and lookups
  • Margin errors found after prices are live
  • Thousands of rows checked by hand, or not at all

With StencilFlow

  • Header row and columns found by pattern recognition, confirmed by a person on one screen
  • Confirmed names remembered, so the vendor's next file maps itself
  • Discount, margin band and rounding applied; gaps go to a person, never a guess
  • A file with only the changed prices, a review file and a summary email

Rules

Checks that run on every case

Your rules and reference data, applied the same way every time. Each outcome records which check passed or failed.

  • Every row matched to a product by EAN, then SKU
  • Margin rule exists for the brand and price band
  • Margin within limits; no big unexplained cost jump
  • No duplicate EAN; pinned prices honoured

Connects to

Hands off to the systems you run

  • Shopify-style bulk upload file
  • PIM or ERP import file

Through an API, an import file or a mailbox. About actions and integrations

In practice

About 19,500 price-list rows checked against the shop in about 12 seconds per run.

Ready to look at your inbox?

Bring one process and a handful of real documents. We show you the path from inbox to decision, on your own data.