SaaSMX
Menu

How it works

The order moves forward through explicit responsibilities.

SaaSMX connects the buyer submission, Stripe payment outcome, merchant decision, kitchen preparation, and final pickup or delivery handoff without treating checkout as the end of the work.

This page explains the controlled sequence. It does not display a live order or promise a connection to every existing system.

  • StateWhere the order stands
  • ResponsibilityWho owns the next action
  • HandoffWhat must happen before work continues

Buyer to completion

One order, seven controlled steps.

Each step names the responsible party, the visible state, and the result required before the next responsibility begins.

  1. BuyerOrder submitted

    The buyer submits the order

    The buyer confirms the supported menu, fulfillment choice, contact details, and checkout information.

    Result: The order details enter the approved checkout and payment path.

  2. StripePayment processing

    Stripe processes the payment

    Stripe applies its payment-processing rules under the merchant's approved configuration and returns the payment outcome.

    Result: The workflow receives an approved or unsuccessful payment result.

  3. SaaSMXOrder recorded

    SaaSMX connects the order record to the payment outcome

    The order path uses the payment result to determine whether the order can continue into merchant review.

    Result: The merchant sees one controlled order record with its next required action.

  4. MerchantReview required

    The merchant reviews the order

    The merchant confirms the supported fulfillment path, resolves any visible exception, and decides whether work can continue.

    Result: Only an accepted and review-complete order moves into preparation.

  5. KitchenIn preparation

    The kitchen prepares the accepted order

    Kitchen responsibility begins after merchant review, with preparation and readiness kept separate from merchant decisions.

    Result: The accepted order advances toward a ready state.

  6. Merchant or approved providerHandoff

    Pickup or delivery receives the ready order

    The merchant completes pickup or transfers the order into the approved delivery handoff without changing who owns each responsibility.

    Result: The final fulfillment responsibility becomes explicit.

  7. MerchantCompleted

    The merchant closes the operational path

    Completion follows the supported pickup or delivery outcome and closes the order's active operational work.

    Result: The order no longer remains in an active work queue.

The sequence is explanatory. Exact capability availability and configuration remain governed by the verified merchant setup.

Payment boundary

Stripe processes payment. SaaSMX controls what follows.

The payment provider and the operational workflow have different responsibilities. The distinction remains visible instead of being described as one undifferentiated system.

Stripe responsibility

Process the payment and govern payment-provider outcomes

  • Apply Stripe payment-processing rules
  • Return the payment outcome used by the order path
  • Handle settlement, account verification, disputes, and provider controls under Stripe terms

SaaSMX does not replace Stripe or decide Stripe settlement, dispute, or account-verification outcomes.

SaaSMX responsibility

Connect the payment outcome to the operational order path

  • Associate the supported payment result with the order record
  • Prevent an unsuccessful payment result from entering normal preparation
  • Present the next supported merchant action

SaaSMX uses the payment outcome for workflow control; it does not become the payment processor.

Responsibility map

Responsibility changes without merging merchant and kitchen work

The merchant controls the order decision. The kitchen prepares accepted work. Pickup or delivery begins only after the order is ready.

Responsibility handoff directionA line with an arrow points from the first responsibility toward the final responsibility.

  1. Buyer

    Provide the order and checkout details

    Next action: Submit the supported order

  2. Merchant

    Review the order and authorize operational work

    Next action: Accept, resolve, or stop the order

  3. Kitchen

    Prepare only the accepted order

    Next action: Advance preparation to ready

  4. Merchant or approved provider

    Complete the pickup or delivery handoff

    Next action: Return the final outcome to the order path

Merchant responsibility

Decide whether and how the order proceeds

  • Review order and fulfillment details
  • Resolve visible exceptions
  • Accept or stop operational work
  • Coordinate the final handoff

Kitchen responsibility

Prepare work that the merchant has accepted

  • Receive accepted work
  • Prepare the order
  • Advance preparation state
  • Mark the order ready for handoff

Attention path

An order needing review does not enter the kitchen silently.

A visible review state keeps the condition, responsible role, and next action together until the merchant resolves the order.

  1. The payment outcome permits the order to enter merchant review

  2. A fulfillment detail or order condition requires a merchant decision

  3. The order remains outside kitchen preparation while review is open

  4. The merchant resolves the condition or stops the order

  5. Only the resolved and accepted order advances to the kitchen

Order-source compatibility

An existing source is qualified before it joins the workflow.

SaaSMX does not assume that every ecommerce or POS source can supply the same data, payment state, fulfillment context, or exception behavior.

Merchant-path comparison

Native ordering and existing sources begin differently

The operational destination may be similar, but the connection path must be verified first.

SaaSMX ordering path

The approved merchant-branded ordering entry point feeds the connected order workflow directly.

  1. Buyer enters through the merchant ordering page
  2. Stripe payment outcome joins the order record
  3. Merchant review controls kitchen release
  4. Pickup or delivery completes the path

Existing order-source qualification

A merchant's current ecommerce source is reviewed before any operational connection is represented as supported.

  1. Identify the source and available order data
  2. Review technical, operational, and commercial compatibility
  3. Define the supported handoff and exception behavior
  4. Activate only the approved connection

Qualification:Existing-source compatibility requires technical, operational, and commercial review. No connection is represented as supported until that review is complete.

Completion

The final handoff closes the active operational work.

Pickup and delivery have different outside responsibilities, but both require a clear supported outcome before the merchant treats the order as complete.

Pickup

The merchant completes the buyer handoff

The ready order is handed to the buyer through the supported pickup process.

Delivery

The approved delivery responsibility takes over

Delivery-provider operations, pricing, and service outcomes remain separate provider responsibilities.

Order record

The merchant closes the active work state

The order leaves active operational work after the supported final outcome.

Review the system boundaries