An approval request is the central unit of work in DiscountFlow. Every time a team member needs to offer discounted pricing to a customer, they create a request — a structured document that captures what’s being discounted, by how much, and why. That request then moves through your organization’s defined approval chain before the pricing can be applied.

What’s in a Request

A request is made up of several parts:

• Request details — A name for the request, the request type, any notes or context for approvers, and values for any custom fields your organization has configured.
• Line items — The products being discounted, with quantities, standard pricing, and the requested discounted price for each.
• Status — Where the request is in the approval lifecycle (Draft, Pending, Approved, Denied, or Archived).
• Approval history — A record of which approvers have acted on the request, what they decided, and when.

Why Requests Exist

Without a formal request process, discount decisions often happen over email, in chat messages, or verbally — with no audit trail and no consistent standard for what gets approved. DiscountFlow replaces that with a single source of truth for every discount decision your organization makes.

Every request is logged, every approval or denial is recorded, and every approved price has a documented decision behind it.

Who Can Create a Request

Any team member with a Member, Approver, or Administrator role can create a request. Creating a request does not automatically submit it — the request stays in Draft until the submitter is ready.

The Request Lifecycle at a Glance

Draft → Pending → Approved
↘ Denied

A request starts as a Draft. When submitted, it becomes Pending and enters the approval queue. It then moves to Approved or Denied based on the decisions of each approval level. Once resolved, requests can be Archived.

For a detailed breakdown of each status, see Understanding Request Statuses.