RetailIntel is India-focused retail intelligence for people making consequential retail decisions.
A multi-agent editorial council reads India’s retail and business publishers around the clock, deduplicates, scores, and publishes signals — with a forecast, a counter-view, and a citation trail — on retailintel.in. Every signal is written to help a decision-maker move, not to pad a feed.
How it runs
RetailIntel runs on cloud infrastructure with a contractual data-boundary for every AI model call: prompts and outputs are never used to train foundation models. Every provider that handles personal data for us is listed in the Privacy Policy.
How a signal is made
Every signal page is bylined By RetailIntel and links here. In a byline, RetailIntel means the automated pipeline described here, built and run by RetailIntel (operated by North Pulse LLC). It is not a named reporter.
Sourcing. Each signal starts from one article by a named publisher, which is linked as the source on the page. The scout agent pulls out the summary, the numbers, the cities and the brands from that article. The first sentence has to carry the actor and a number or date when the article gives one. A summary that misses this, or states a number the article does not contain, is sent back once for a rewrite; if the rewrite misses too, the first version stands.
Deduplication. A story is published once. If another feed carries the same canonical URL, a very close rewrite of a story from the last six hours in the same theme, or another publisher’s report of the same event within 48 hours, it is recorded as a further source on the existing signal instead of a new page, and any earlier duplicate page redirects (301) to the one we keep. Every other publisher that carried the event is named under the headline as Also reported by or Confirmed by.
Review
The scout drops items that are not about retail that matters in India, and the editor agent drops stories it scores as too thin to be worth a page. Accepted stories then get a counter-argument pass: a model argues against the reading and records a counter-case with the signal. A signal page shows that counter-case under The counter-case, captioned as not reported by the source, only when the record exists and every figure in it also appears in the source. The pass records dissent. It does not block publication, and it is not a fact-check by a person.
The search summary, key facts and watch items shown on a signal page are checked against the extracted source facts every time the page is rendered. Anything that does not match is dropped and the plain source summary is shown instead.
How an Ask answer is made
A saved Ask answer is bylined Answered by RetailIntel and links here. As on signal pages, RetailIntel means the automated pipeline built and run by RetailIntel, not a named person. The answer is written when a reader asks, from the published signals and forecasts that match the question. Each claim carries a cite to one of those signals; a cite to anything else is removed before the answer is shown. No person reviews an answer before it is shown.
A saved answer keeps the day it was asked in its address and is not rewritten later: asking the same question again gives that day’s read. A cited signal that is later withdrawn drops out of the page’s cites and charts.
Corrections
If a signal is wrong, report it to us. A corrected signal shows a later modified date in its page data. A signal replaced by a better copy of the same story permanently redirects to that copy, so old links and citations still resolve. The full policy is on /corrections. How fast we publish, the old news we keep out and every correction we log are counted hourly on the track record page.
Contact
Editorial questions, partnerships, or access requests — write to RetailIntel. To fix a signal, see corrections; to report a vulnerability, security.