Number of Seats/Users: Dimensions offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Dimensions that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Dimensions. Dimensions reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Dimensions offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Dimensions. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Dimensions often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that feedback on Dimensions is quite mixed, but with some clear patterns that can help you buy and use it smarter.

Overall sentiment
Most Spendbase clients say Dimensions is:

• Technically solid and stable
• Reliable in terms of data integrity
• Less impressive when pushed beyond its core purpose

What Spendbase clients like

Our internal data shows that the strongest positives are:

• High stability
• Systems rarely crash during peak hours

• Good performance even with large transaction volumes

• Data integrity

• Transaction records are consistent and trustworthy

• Low risk of losing sales or inventory data

• “Set and forget” operations

• Once configured, daily use tends to be smooth
• Works as a dependable backbone for restaurant or retail flows

Where clients get frustrated

At the same time, Spendbase clients flag a few recurring issues:

• Misuse as a development or code tool
• Some teams tried to use Dimensions as a source code or version control system
• Our internal data shows this leads to poor experience and low satisfaction

• It is not suited as a primary code repository or dev workflow manager

• Functional mismatch

• When companies try to stretch it far beyond POS and simple store ops, value drops fast
• Complex lifecycle management or engineering use cases are especially painful

Spendbase recommendations (from a cost and discount angle)

Based on client outcomes, here’s how to avoid overspending:

• Keep Dimensions in its lane
• Use it for what it does best: running restaurant/retail operations and POS

• Avoid paying for additional seats or modules just to use it as a code or repository tool

• Right-size licenses

• Limit access to operational staff who truly need it

• For technical teams, shift code and version control to dedicated tools and reduce Dimensions usage there

• Leverage this in negotiations

• Highlight that your main use is stable POS, not advanced lifecycle or dev features
• This often justifies a tighter package and stronger discounts in contracts and renewals