From the closed week to Monday's review.

One week in Kelynto, start to finish: what the system does without anyone watching, what your planner does, and who owns each step. The days below are an example. You set the fiscal week, the time zone and the hour the review is drafted.

The week, step by step.

Seven steps. Four run on their own. Three belong to your planner, and those are the ones that decide what leadership reads.

  1. Fridayor whenever your week closes

    The closed week's file arrives

    Your planning system, your warehouse or an analyst exports the week that just closed: actual sales and plan by store and category. In-stock rates and promotions come along if you send them. The file is uploaded in the app, sent to the inbound API by a scheduled job on your side, or collected by Kelynto on a schedule from an SFTP folder or a storage bucket your admin names.

    Nothing is installed in your network. Kelynto reads only the files you send or leave in that folder.

    Owner Your data team or an analyst

  2. On arrivalseconds to minutes

    Every file is checked before it is loaded

    The loader reports how each column was read and names the rows it could not read. A file with errors in more than one row in five is rejected outright, and the data already loaded is left unchanged, so a bad export cannot overwrite good weeks. Every load is read back from the database before it is kept, and a load that does not read back as accepted is rolled back.

    A recurring export can go further. Under its source profile, a file whose columns changed, whose control totals do not reconcile to the cent, or that would change a published review is held, and nothing of it loads. The hold shows exactly what the file would change, row by row, until an admin or analyst decides it with a reason; whoever sent it does not approve it while someone else can. Every file is in a delivery history that can be downloaded.

    Sending the same file twice is safe: rows are matched and updated, not duplicated, and under a source profile a file received before is recognised and not loaded again.

    Owner Kelynto checks. An analyst reads the report and fixes the export if needed. An admin or analyst decides a held file.

  3. Before the runautomatic

    Outside signals are refreshed

    Weather alerts and forecasts are looked up for your store coordinates. Local events and road work are added if an administrator has switched those sources on. Facts only your team knows, such as a competitor opening or a remodel, are recorded on the Watch page or sent in a signals file.

    A source that fails does not stop the week. The review is drafted with the signals that arrived.

    Owner Kelynto. An admin chooses which sources are on.

  4. Monday 6:00the default, in your time zone

    The review is drafted

    The weekly run adds up the shortfalls and the lifts of each store and category apart, for the company and for each region, store and category, and sets the week out in three parts: causes your own records show, each with an estimated impact credited where its records sit; weather, local events, road work and competitor openings on file near a store, with place and dates; and every shortfall not explained. It also lists what is on file near each store for the next three weeks, and names the files the review was produced from.

    The commentary is then written from those three parts by Kelynto's built-in writer, or by Claude when the AI writer is switched on for the workspace, and every figure in it is printed from the week's evidence. The method is set out step by step on the Methodology page.

    Owner Kelynto. You set the day and the hour.

  5. Monday morningthe planner's part

    The planner reads, checks and corrects

    The draft is already written when the planner opens it: the headline variance, then the week in three parts for the company and for each region, store and category. The planner opens the record behind each recorded cause and confirms it, rejects it, or corrects it to the cause they know is right. They can say whether a record on file mattered, name a cause for what is not explained, add a cause the review missed, and assign follow-up actions with an owner and a due date. Then they edit the wording in their own voice; each save is checked for figures that match nothing in the week, and every version and every decision is kept.

    They also mark each Watch item as new to them, already known or not relevant.

    Owner Planner

  6. Mondaybefore the business review

    The planner publishes and sends it up

    Nothing reaches leadership until the review is published. The published review downloads as a Word document, a PDF or a PowerPoint deck, goes by email to members and to addresses at domains the admin has approved, can be shared as a read-only link where the admin allows links, or can be copied into email or slides. A member limited to some stores receives the review of their stores. Leaders with a viewer role can read it in the app. A published review can be reopened, and every version is kept.

    Once it is published, the planner answers two questions: how many minutes the review took, and whether they would use this every week.

    Owner Planner. Leadership reads.

  7. The weeks afterautomatic

    The week is scored

    The planner's labels are counted in planner agreement and in the correction and rejection rates. The difference between the draft and the published text becomes the edit rate. When the next weeks' sales arrive, they are set beside what the review said and what planners decided, as facts.

    All of it lands on Score and learn, which the planning leader reads to decide whether this is earning its place.

    Owner Kelynto computes. The planning leader judges.

Planner time is measured on your own weeks: the pulse questions record the minutes each review took and whether the planner would use it every week.

Around the same week. A recap workbook can be dropped as it is on the first step, including a sheet laid out as a grid. The draft opens with a line that sets this week beside the week before, and under the three parts a panel says in words what carries into next week. Store and district managers can leave a short, dated note for one of their stores, shown to planners as context. Once the review is published, the Monday email can send each member the review of their own stores, and Export gives the recap for leadership as a workbook, slides and email text. The Outlook turns the same records forward, for the weeks ahead. The detail.

Who does what.

Four roles inside the product, checked on every request, and three jobs outside it. With single sign-on the roles come from your identity provider, so removing a role there removes the access.

RoleWho it suitsWhat they do
ViewerLeadership, store operationsReads published and in-progress reviews, Watch and Score and learn.
PlannerDemand and merchandise plannersEdits the commentary, confirms, rejects or corrects causes, adds causes and follow-up actions, marks Watch items, publishes.
AnalystPlanning or data analystsEverything a planner can, plus uploading data, source profiles and held deliveries, re-running a week and exporting the labelled dataset.
AdminThe workspace ownerEverything, plus users and their store access, workspace settings (fiscal week, time zone, thresholds, signal sources, schedule), single sign-on and provisioning, API keys, retention, the full export and the audit log.
Your data teamOutside the productBuilds the weekly export, by hand at first and as a scheduled job later.
Your IT teamOutside the productRegisters the application in your identity provider, assigns the four roles, and can connect SCIM provisioning.
Kelynto operatorOutside the productCreates the workspace and can register your identity provider, which your admin can also do in the product. In a pilot, can run the first weeks by hand.

Access by region, district or store. An admin can limit a member who is not an admin to the stores of some regions, districts or stores of your stores file. That member then reads those stores only, on every page, document, email, export and answer, with none of the company's totals, and the limit is enforced in the database as well as in the application.

What goes in.

Two files are enough for a first review. Everything is weekly totals.

  • Stores. One row per store, with a store number and region. Add coordinates, and weather, events and road work are matched to each store.
  • Sales against plan. One row per store, week and category, with actual and plan.
  • In-stock, if you have it. It is what makes a stockout visible in the review, with an estimated amount beside it.
  • Promotions and local facts, if you have them. One row per promotion or per fact.

The full list of files and columns

What comes out.

One review a week, and a record of what your planners made of it.

  • The published review, in the planner's final words, with the record behind each recorded cause and the amount not explained.
  • Watch, what is on file for the weeks ahead, with each planner's mark on each item.
  • The decision history and follow-up actions, with who decided what and when.
  • Score and learn, three measures with their sample sizes.
  • A labelled dataset you own: each record, the part of the review it sat in, the cause a person confirmed, and the outcome. It can be exported at any time.

When something goes wrong.

Weeks are not always clean. This is what happens in the cases that come up.

  • The data is late. The scheduled run is tried again about an hour after a failure, four attempts in total by default, so a file that lands mid-morning is picked up the same day.
  • The export is wrong. The file is rejected with a report that names the columns and rows at fault. Nothing is loaded and existing data is untouched.
  • The export changes shape, or does not add up. Under a source profile the delivery is held with the exact difference: a column gone or new, or control totals that do not reconcile. An analyst accepts the change as the profile's next version, or the sender fixes the export.
  • Corrected figures arrive after publishing. The published review stays as it was and says its data changed. The week is run again with every decision carried over, and the restatement says what it replaces when a planner publishes it.
  • A run is interrupted. It is marked failed with its reason, so nobody reads a half-finished week, and the week is run again.
  • No record supports a cause. Nothing is credited. The amount stays in not explained, and a promotion on the calendar with no estimate to state is listed as such.
  • The draft names the wrong cause. The planner rejects or corrects it before anything is published. Each rejection is kept as a label and shows in planner agreement and the rejection rate.
  • Two people edit at once. The second save gets a clear conflict message. Nothing is silently overwritten.

Before the schedule exists.

A pilot does not have to wait for single sign-on or an export job.

  • The first weeks can be run by hand. You send the week's files, a Kelynto operator runs the week and sends the exported commentary by email.
  • Your planner replies with edits and verdicts, and the operator enters them on the planner's behalf. The edit rate and planner agreement are measured the same way.
  • It is written down. In this mode Kelynto handles your files and enters your planner's feedback on their behalf, and the pilot agreement says so.

See it on your own weeks

  • The whole week on this page runs in the product, and the product tour shows it on a synthetic retailer
  • Kelynto Managed runs on Microsoft Azure in Central US, deployed by an automated pipeline with health checks and automatic rollback
  • Each outside signal source is switched on per workspace
See what a pilot involves Or book a 20-minute conversation

Five ways to take the next step.

  1. Explore

    See the product

    The product tour shows real screens of the product on a synthetic retailer, in the order a week runs.

    Take the product tour

  2. Evaluate with your data

    Run it on your own weeks

    Eight sealed weeks of your own history, run once and scored against bars fixed before anyone sees a result, then about eight live weeks.

    See what a pilot involves

  3. Review the security

    Check every control

    Kelynto Managed on Microsoft Azure or in your own Azure account, what crosses the boundary, and every control with its status and evidence.

    Open the Trust center

  4. Offer it to your clients

    Build it into your service or product

    For planning services, retail software vendors and consultancies: the partner API, embedded views and your brand, starting with a sandbox of synthetic clients.

    See the partner platform

  5. Talk to us

    Twenty minutes with the founder

    Your process and your questions. Or write to marc@kelynto.com.

    Book a 20-minute conversation