A clean core.
A connected business.

Standardizing the ERP does not remove the business logic around it. Understand the rules that connect your core system, service layer, and day-to-day decisions.

Enterprise systems

A clean core. A connected business.

Understand the business rules that connect your core system, service layer, and day-to-day decisions.

Scroll to navigate01 / 08

Enterprise systems

A clean core. A connected business.

Understand the business rules that connect your core system, service layer, and day-to-day decisions.

Scenario / Airline

Cancel for free within 24 hours of booking.

One cancellation rule appears in five places. Explore what each says, and where the promise changes.

Booking website / Choose your fare

Book with confidence.

  1. Customer promise24-hour cancellation promise
  2. Policy24 hours + seven-day departure condition

Cancel for free within 24 hours of booking.

Fare rules / Section 4.2

Your cancellation rights

  1. Customer promise24-hour cancellation promise
  2. Policy24 hours + seven-day departure condition

Cancel without penalty within 24 hours, provided your booking is made at least seven days before departure.

Reservation setup / Example configuration

Cancellation eligibility

  1. Policy24 hours + seven-day departure condition
  2. ConfigurationMinimum time to departure: seven days

The departure threshold is part of the active fare rule.

Example API / cancellation.ts

Refund eligibility

  1. ConfigurationMinimum time to departure: seven days
  2. Booking APIChecks the booking window and departure date

The service checks both the booking window and the departure date.

Customer care / Example conversation

A customer asks for help

  1. Booking APIChecks the booking window and departure date
  2. OperationsDeparture within seven days: not eligible

I booked this morning and fly in three days. The website says I can cancel for free. Can you help?

Difference to review / Commercial policy owner

Cancellation condition missing from website

Customers departing within seven days may expect a refund the system declines.

The core is only part of the story.

A discount rule connects commercial policy, ERP configuration, and service logic. The surrounding assumptions matter when the core changes.

  1. 01
    Commercial policy

    Who qualifies?

    Customer groups, products, and agreed exceptions.

  2. 02
    ERP configuration

    What is configured?

    The value and applicability in the core system.

  3. 03
    Service layer

    What is applied?

    Eligibility checks and order-level transformations.

How Haster helps

Know what
connects the core.

Your distinctive business logic may live in services around the ERP: pricing, approvals, eligibility, order routing, and exceptions.

When a core configuration changes, the impact may depend on those surrounding rules. When a service changes, the assumptions in the core still matter.

Haster's proposed approach is to follow a rule from the business instruction through service code and ERP configuration. Business and technical owners review the sources together before deciding what needs to change.

Different businesses. The same need for clarity.

  • From customer instructions to accounting

    A vessel manager receives new expense-account instructions by email. Finance still works with the old posting rules. Following the instruction through the service layer and ERP setup helps reveal where it was missed, before more entries need reclassifying.

  • Different divisions around a shared ERP

    Grocery, foodservice, and food processing divisions share a standard ERP, but keep their own pricing and order rules in services around it. A rule that is right for one division may be wrong for another. Owners need to see where each rule applies before changing a shared service.

One change
across the boundary.

01Define the business behavior

Choose a rule with an identifiable owner, a clear outcome, and relevance to both the core and service layer.

02Examine its expressions

Review the relevant configuration, service code, API definitions, and policy with agreed permissions.

03Decide with evidence

Document intentional exceptions and review discrepancies. Your team owns the decisions and any resulting system changes.

Your technology stack

Start with your
existing systems.

For organizations working with Microsoft Dynamics 365 or other ERP environments, we begin by understanding where the relevant rules live and how they can be accessed.

Source access, exports, and any integration development are agreed during scoping. Dynamics 365 is a relevant environment for this work; a ready-made connector is not currently offered.

Our forward-deployed team works with your business and technical owners throughout setup and validation.

What changes
around your core?

Choose your solution

Replay intro