Features

BBG Sentinel is Better Be Goods BV’s Amazon channel intelligence platform: it is being built to monitor Seller Central and Vendor Central accounts continuously through the Selling Partner API, detect anomalies, and raise prioritised alerts for the people who run those accounts.

This page is the precise version. The overview makes the case for why we are building it; what follows is a plain statement of what exists today, what does not, and what we have decided not to build at all.

Status at a glance

Capability	Status
Credential store, token issuance, per-organisation isolation, audit log, admin interface	Live
First-line monitors — Buy Box and the first alerting agents	In development, not live
Inventory and catalogue signal agents	Designed, not built
Cross-account and business-level agents	Designed, not built
Advertising intelligence	Planned — requires a separate Amazon Advertising authorisation we have not applied for
Forecasting and planning	Out of scope
Autonomous actions, including repricing	Out of scope by design — see below
Meta-agent and business intelligence	Out of scope

No monitoring agent is live yet. Where this page describes an agent, it describes something being built, not something running.

What runs today

One credential store

A brand authorises BBG Sentinel once. The resulting SP-API refresh token is stored in a single database, encrypted at rest with Fernet symmetric encryption. The encryption key is held in Google Secret Manager and is not present in source code, container images or configuration files.

Downstream systems never receive the refresh token. They receive a short-lived access token when they ask for one, and nothing else.

Short-lived access tokens

Services request an access token per unit of work and discard it afterwards. Because BBG Sentinel is the only holder of the refresh token, an internal system that is decommissioned, rebuilt or compromised does not take a long-lived Amazon credential with it.

Per-organisation isolation

Every credential, authorisation and audit record belongs to exactly one organisation, and access is enforced at the row level. One brand’s Amazon accounts are not visible to the systems or operators of another brand, even though they share the same installation.

Access is granted to a service, not handed to a person as a copied secret.

Append-only audit log

Every token issuance is written to an append-only audit log recording the requesting identity, the organisation, the time and the outcome. Entries are not editable or deletable through the application, so the log can answer “which system used this brand’s credential, and when” after the fact.

The admin interface

Connecting an Amazon account, reviewing which authorisations exist, and revoking one.

Built on managed infrastructure

• No static database passwords. The application authenticates to its database using short-lived Google Cloud IAM tokens. There is no database password to rotate, leak or check into a repository.
• Encrypted connections only. The managed database instance is configured to reject unencrypted connections. Traffic between components, and between BBG Sentinel and Amazon, is over TLS.
• Least-privilege runtime service accounts, separated per component. Nothing runs under a shared administrative identity, and each component gets only the permissions it needs — for example, permission to read one secret rather than all of them.
• Runs in the EU. The application and its database are hosted on Google Cloud in region europe-west4.

What is in development

The first-line monitors are the agents being built now: Buy Box loss, and the alerting path that carries a finding to the person who needs it. The overview describes the full catalogue we are working toward and what each agent is meant to catch.

Every agent in that catalogue is covered by an SP-API role we have already requested. We are not describing capabilities that would need access beyond our application.

What BBG Sentinel will not do

These are decisions, not gaps.

• No autonomous actions. No agent ships in auto mode. BBG Sentinel is being built to tell a person what changed and what it is likely to cost. It does not change prices, edit listings, or act on an account on its own, and that is a deliberate architectural commitment rather than a limitation we intend to lift.
• No repricing. For the same reason.
• No buyer personal data. The restricted SP-API roles that expose buyer names, addresses, phone numbers and email addresses were deliberately not requested. Buyer personal data is therefore never retrieved, never transmitted through BBG Sentinel, and never stored by it.
• No advertising data without a separate authorisation. The Amazon Advertising API is a separate developer application. Until it is applied for and approved, no advertising data reaches BBG Sentinel.

Availability

BBG Sentinel is operated by Better Be Goods BV for its own group companies and for partner brands under agreement. There is no public sign-up. See Pricing for how access is arranged, or get in touch with a question.