Skip to main content

Pilot program

The Pilot program is for supermarkets that Tradar wants to onboard closely before they become normal paying customers.

A supermarket in Pilot gets live access to Tradar, but payment for its selected pricing tier is waived during the pilot period. The goal is to let the store prove the workflow with real products, real orders, real staff, and real operational support before the commercial relationship starts.

What Pilot means​

Pilot is a state on the supermarket account, not a permanent free plan.

While FreshMart is in Pilot:

  • It can use the supermarket app, storefront, catalogue, inventory, order desk, payments, payouts, and rider workflow.
  • It should be assigned the pricing tier that fits its catalogue size, even though payment is waived during the pilot.
  • It should be visible to Tradar admins as a Pilot supermarket.
  • It should have a start date, an expected end date, and a clear owner inside the Tradar team.
  • It should have a conversion decision before the pilot ends.

Pilot does not mean the supermarket can ignore operational requirements. It still needs a real store profile, working contact details, valid payout details, products, opening hours, and a rider setup before it can operate properly.

What is included​

The recommended Pilot access level is full access to the selected tier for a fixed period.

For example, if FreshMart needs the Growth tier because it has more than 5,000 SKUs or needs API access, Tradar can mark it as Pilot on Growth. FreshMart gets Growth level access during the pilot, but the Growth subscription fee is waived until the pilot ends.

This keeps the test honest. A supermarket should evaluate the product it would actually use after conversion, not a limited demo that behaves differently from the paid account.

What should be limited​

The limit should usually be time, not feature access.

A typical pilot should have:

  • A defined start date.
  • A defined end date, usually 30, 60, or 90 days.
  • A named commercial owner.
  • A target outcome, such as launch the catalogue, process first orders, train staff, or validate a branch workflow.
  • A decision at the end: convert to paid, extend the pilot, downgrade to Open, or suspend access.

Usage limits can still be added when needed. For example, Tradar may cap the number of branches, staff seats, imported SKUs, API calls, or custom integration work during the pilot.

After the pilot​

Before the pilot end date, the Tradar team should decide what happens next.

Convert to paid. The supermarket keeps its tier, the pilot waiver is removed, and normal billing starts.

Extend the pilot. An admin updates the pilot end date and records why more time is needed.

Move to Open. If the supermarket is not ready to pay and fits within the Open limits, it can stay on the free tier.

Suspend or close. If the supermarket is not a fit, access can be suspended without deleting its history.

Pilot should always end with a deliberate decision. It should not drift into unpaid full access with no owner.