ACTELUS
Discuss a workflow

Supplier price updates, ready for review.

A supplier sends a new price list. Somebody then spends a day or two working out which of your own catalogue lines actually changed, and by how much. This is a fixed-scope pilot that does the comparison and hands you the result to approve.

This is a pilot offer, run on a real sample of your data. No completed client engagement is published for it yet, and no saving is promised here.

Scope
One supplier, one comparison
Size
Up to 500 SKU rows
Target turnaround
About 3 working days
Writes to your ERP
Never

Then the real work starts

  • Supplier codes are not your codes

    The file arrives in the supplier’s structure, with their references and their descriptions. Matching it to your catalogue is the job, and it is manual.

  • Most rows did not change

    The lines that matter are buried among hundreds that are identical to last quarter. Finding them by eye is slow and easy to get wrong.

  • Missed increases are absorbed as margin

    A price that goes up without being passed through stops being visible. It just reduces the margin on that line, quietly, until someone notices.

  • It happens again next quarter

    The work is not one-off, so the cost repeats. That is usually what makes it worth automating rather than enduring.

supplier-prices-q3.csv What arrives
Reference Price
NF-2211-TE25 72.10
nf 9043 mcb16 Their casing, not yours 4.12
NF-5521-FLTG4 11.20
NF-7740-CU8SP The same line again 151.75
NF-1180-VNT30 No price given none
… 408 more rows
price-change-review.xlsx What you approve
SKU Old New Outcome
CBL-TE-2.5-100 68.40 72.10 Matched
MCB-B16-6KA 3.95 4.12 Matched
HVAC-FLT-G4-595 11.20 11.20 No change
CU-8W-SPD 142.00 151.75 Matched
— — 18.60 Needs review
412 catalogue rows compared · 381 matched · 23 flagged for review · 8 supplier rows with no catalogue match Illustrative interface Synthetic catalogue and supplier data, not a client file.

One supplier, one comparison

Scope of the pilot

  • One supplier.
  • One old price list and one new price list.
  • Your product catalogue extract.
  • One import template, in the format you already use.
  • Up to 500 SKU rows.

The row limit keeps the pilot small enough to judge quickly. Larger files are quoted after scoping, once the structure of your catalogue is known.

What you get back

  • A structured change file, shaped for your import template.
  • A separate list of unmatched or uncertain rows, each with the reason.
  • Where the data supports it, a summary of the potential margin impact of the changes.

Price

The pilot is priced per engagement and confirmed in writing before any work starts. Tell us the supplier and the rough catalogue size and you will get the figure with the scope.

Ask for the scope and figure

Four steps

  1. Scope the sprint

    You provide
    The supplier in question, and roughly how many catalogue lines it covers.
    We return
    Confirmation of whether it fits the pilot scope, and what inputs we need.

  2. Agree the inputs and how they reach us

    You provide
    The old and the new price list, your catalogue extract and one import template.
    We return
    A transfer method agreed with you, and a written list of the exact files in scope.

  3. Reconcile the lists

    You provide
    A contact for questions about product codes and conventions.
    We return
    A structured change file, plus a separate list of rows that are unmatched or uncertain.

  4. Review the output together

    You provide
    A look over the flagged rows and a decision on the ones we could not match.
    We return
    Corrections, a note of any pattern worth fixing in the catalogue, and the final file.

The three working day target applies to the reconciliation step, measured from the point where the inputs have arrived and the scope has been accepted.

What this does not do

Worth reading before the FAQ, because it is the part that decides whether this is useful to you.

It does not change live records
No write access to your ERP, pricing tables or catalogue. The output is a file. Your approval and import process is untouched.
It does not guess uncertain matches
A row that cannot be matched confidently is listed as unmatched, with the reason, for a person to decide.
It does not replace your approval process
Somebody in your business still signs off the changes. The sprint changes how long it takes them to get to that point, not who decides.
It does not promise a saving
We have not measured your process, so any figure would be invented. What is offered is a defined scope, a defined output and a defined turnaround.

Before you enquire

What exactly do I get at the end?
A structured change file covering the lines we could match confidently, a separate list of rows that are unmatched or uncertain, and where the data supports it, a summary of the potential margin impact of the changes.
Does this touch our ERP or pricing system?
No. The sprint never writes to a live ERP or price record. The output is a file for your own approval and import process, which stays exactly as it is today.
How long does it take?
The target is about three working days from the point where the inputs have arrived and the scope has been accepted. Scoping and the file transfer happen before that clock starts.
Our price list is much larger than 500 rows.
The pilot is deliberately a sample: one supplier, up to 500 SKU rows, so you can judge the output on your own data without a large commitment. Larger files are quoted after scoping, once we have seen the structure of your catalogue.
What about rows the system cannot match?
They are never guessed. Unmatched and uncertain rows are listed separately with the reason, so a person makes the decision. In most catalogues these are the rows worth looking at anyway.
How do we send you the files?
Not through this website. We agree a transfer method with you after scoping, so nothing commercially sensitive is uploaded through a web form.

Why this takes two days by hand, and which rows genuinely need a person, is written out in why a supplier price list takes two days to check.

Start with the supplier

That is enough for a first reply. Please do not attach price lists or any other commercially sensitive file: the transfer method is agreed after scoping.

Discuss a price-list pilot

The more concrete the process, the more useful the reply. Volumes, the systems involved and where the time goes are the three things we always ask about.

Enter your name.
Enter the business name.
Enter a valid business email address.
Choose one of the listed areas.
Describe the process in a sentence or two, so we can tell you if it fits.

Do not attach supplier files or client documents here. If a file transfer is needed, we agree the method after scoping.

What you send is used to answer your enquiry and nothing else. It reaches us by email through Resend, is not added to a marketing list, and is deleted within 12 months if it does not lead to work. How your data is handled.

What happens next

  • A reply on whether the supplier and catalogue fit the pilot scope.
  • The inputs we would need, and a transfer method agreed with you.
  • The figure and the scope in writing, before any work starts.