Skip to content

Aperture Docs

What Aperture does, how the flows work, and quick answers when you're stuck. Every fact is verified against the code, not someone's memory of it.

Aperture is a competitive pricing intelligence platform. It tracks what competitors and retailers charge for products, so you can see where your own prices sit in the market and act when they move. Retailers use it to compare themselves against competing sellers. Brands use it to watch how the retailers carrying their products price them, and whether those prices respect MAP rules.

Features

Every part of Aperture, explained for the people who use it: MAP violations, alerts, products, movers, equivalents, and more. Each entry covers what it does, what you see on screen, and how to act on it.

Flows

End-to-end walkthroughs of how things happen, from first sign-in and demo data through to live monitoring. Each one traces the real code paths, step by step.

FAQ

A searchable answer bank for the questions that come up in practice. Press / anywhere on this site to search every page and answer.

Always current

These docs are regenerated and re-verified against the Aperture codebase. When the product changes, the docs follow. When a page can’t be verified, it doesn’t publish.

Every page here is produced by a documentation pipeline that reads the actual Aperture source code:

  1. Written from code. A writer derives each page from the codebase itself, with the product specs as context and the code as the source of truth.
  2. Cross-reviewed. An independent reviewer re-checks every factual claim on the page against the code, line by line. A page publishes only when every claim is verified.
  3. Fail-closed. If a claim cannot be verified, the page keeps its last verified version instead. You never read something that did not pass review.