Number of Seats/Users: ABW 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 ABW 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 ABW. ABW reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: ABW 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 ABW. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: ABW 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 ABW tends to land very well with most Spendbase clients, especially those running several entities and warehouses on one stack.

Key positives our clients highlight:

• Easy to work with
• Interface is considered intuitive once set up.
• Day‑to‑day users say it “feels friendly” and doesn’t require deep technical skills.
• High flexibility
• Many modules / “categories” make it possible to model different processes and designs.
• Strong support for:
  • Multiple companies
  • Multiple warehouses
  • Multiple currencies
• Single SQL Server backend
• IT teams like having one central database.
• Reporting and integrations into BI tools are simpler and cheaper to maintain.

Main pain points we hear:

• Choice overload
• Because there are so many categories, layouts, and configuration options, some clients struggle to decide which “design” or setup to use.
• This can slow down initial implementation and increases dependence on consultants.
• Configuration effort
• Power and flexibility come with a setup cost. Smaller teams sometimes feel they are “over‑configuring” just to use a subset of features.

How our clients actually use ABW:

• Most use a core set of modules heavily (finance, inventory, multi‑warehouse), while leaving some peripheral modules unused.
• Power users invest in custom views and designs to make operational screens fit their exact workflows.
• Centralized SQL data is often leveraged for custom reports instead of relying only on built‑in ones.

Discount and cost‑optimization insights (from a Spendbase angle):

• Many clients initially overbuy modules “just in case” but later discover they could drop or downgrade some without impact.
• Our internal benchmarks show meaningful savings by:
• Standardizing on a narrower set of modules across entities.
• Rightsizing user types (power vs casual users).
• Negotiating bundled pricing when multiple companies share the same ABW instance.
• Clients that document which “designs” and categories are truly used can usually cut 10–20% of unused capacity during renewal.

Overall, ABW is seen as a flexible, user‑friendly ERP with strong multi‑entity capabilities, where smart module selection and license tuning can significantly reduce total cost.