Skip to main content

Changelog

Follow new updates and improvements to Appliance.io.

Appliance.io Updates & Improvements (May 25th, 2026)

✨ Update: Improved T&C Signing Flow with Fulfillment Validation

What’s New

  • Added fulfillment validation before Terms & Conditions (T&C) signing in the Customer Portal

  • Customers can only access the T&C signing step when all order items have fulfillment configured

  • Introduced automatic transition from T&C signing to payment for a continuous order completion experience

  • Added Customer Portal stepper with T&C as the first step

  • Improved T&C presentation and document organization across Customer Portal and Website

  • Added safeguards to prevent sending payment links before orders are fulfillment-ready

Behavior Updates

  • Customer Portal access for T&C signing is now gated by fulfillment readiness

  • If one or more items are missing fulfillment:

    • Customer Portal access is restricted

    • Customers will see the message:
      “Set fulfillment for all items to enable portal access”

    • “Send Email with Paylink” changes to “Send Invoice without Paylink.”

    • Hover tooltip explains why payment access is unavailable

  • After successful T&C signing:

    • Customers are automatically guided into payment

    • No additional navigation or manual follow-up is required

  • T&C display behavior has been improved:

    • General T&C appears in a cleaner, scrollable layout

    • Brand-specific and condition-based T&C include product count indicators

    • Duplicate T&C documents are automatically prevented

  • Website T&C behavior now follows the same experience as the Customer Portal across desktop and mobile

Why This Matters

  • Prevents customers from progressing through incomplete orders

  • Eliminates dead-end experiences after T&C signing

  • Reduces manual follow-up from Sales teams

  • Creates a more connected and predictable order completion journey

  • Improves visibility and clarity of applicable Terms & Conditions

Appliance.io Updates & Improvements (May 18th, 2026)

✨ Update: Prevent Duplicate Payments Across POS, Customer Portal, and Website

What’s New

  • Added duplicate payment protection across:

    • POS

    • Customer Portal

    • Website checkout

  • The system now blocks additional payment attempts when:

    • A payment is already processing

    • An order has already been paid for

  • Added clearer “payment is processing” handling during checkout and payment submission

Behavior Updates

  • Payment buttons are temporarily disabled while payment is processing

  • Users attempting a second payment during processing will see:

    • “Payment is being processed in another session.”

  • Duplicate payment protection now works across:

    • Multiple browser tabs

    • Different devices

    • Different payment channels (POS, Customer Portal, Website)

  • Users can retry payment immediately if the previous attempt fails, is canceled, or returns an error

  • Refreshing or retrying will not create duplicate successful charges for the same order

Payment Flow Improvements

  • Reduces accidental duplicate payments caused by:

    • Multiple tabs

    • Repeated clicks

    • Simultaneous payment attempts across channels

  • Improves clarity when payments are actively processing

  • Creates more predictable payment behavior across all supported payment experiences

Why This Matters

  • Helps prevent duplicate charges for customers

  • Reduces refund handling and reconciliation work

  • Improves payment reliability and customer confidence

  • Creates a more consistent payment experience across POS, Website, and Customer Portal

Additional Notes

  • Most payments are complete within a few seconds

  • If payment remains in processing for more than 1 minute, users can refresh the page and retry if needed

  • This release does not introduce new payment methods or pricing changes

Appliance.io Updates & Improvements (April 23th, 2026)

✨ Update: Payment Protection & Processing Experience

What’s New

  • Added safeguards to prevent duplicate payments across POS, Customer Portal, and Website

  • Improved payment flow to clearly indicate when a transaction is in progress

  • Enabled safe retry for failed payments without risk of duplicate charges

  • Standardized payment behavior across all channels

Behavior Updates

  • Users can no longer submit multiple payments for the same order while a payment is in progress or already completed

  • Payment actions (e.g., “Pay” button) are temporarily disabled during processing

  • Users receive clearer feedback when a payment is underway

  • Failed payments can be retried safely without creating duplicate successful charges

Why This Matters

  • Reduces risk of double charges and associated refunds

  • Minimizes operational overhead for reconciliation and support

  • Improves accuracy in payment reporting

  • Creates a more reliable and predictable payment experience across all touchpoints

Earlier updates