# Haster | Consolidate control.

Source: https://haster.ai/

Connect business rules across policies, configurations, APIs, and code. Investigate inconsistencies and the impact of change with source-linked evidence.

## Consolidate control.

Haster gives you a central command center for all your business rules that are scattered across your policies, configurations, APIs, custom service layers, business applications and code.

## One business rule. Many places it can break.

This fragmentation is costly, time-consuming and risky. With Haster, you regain complete control.

## From scattered sources to shared understanding.

- Less manual investigation. Less wasted time.
- Better visibility into inconsistencies and dependencies.
- Shared understanding between business and technology teams.
- Faster delivery. More confidence.

## Great people don’t grow on trees.

We’re building a team of exceptional people who care about difficult problems and the craft of solving them.

A focused collaboration with our forward-deployed team, around your business and your technology stack.

Agree the scope together. Put it to work. Review the value before deciding what comes next.

## Airline: scenario

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

### Customer promise: Book with confidence.

Reference: Booking website / Choose your fare

Cancel for free within 24 hours of booking.

- Journey: Oslo → London
- Fare: Flexible start

Fare rules: free cancellation only when booked at least seven days before departure.

The website leaves out the seven-day condition.

### Policy: Your cancellation rights

Reference: Fare rules / Section 4.2

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



Website: cancel for free within 24 hours of booking, with no departure condition stated.

The policy promises less than the website.

### Configuration: Cancellation eligibility

Reference: Reservation setup / Example configuration

The departure threshold is part of the active fare rule.

- Free cancellation window: 24 hours
- Minimum time to departure: 7 days
- Outside eligibility: Fare cancellation fees apply

Website: the same 24-hour window is shown without the seven-day threshold.

The configured condition is missing from the customer promise.

### Booking API: Refund eligibility

Reference: Example API / cancellation.ts

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



```typescript
const eligible =
  hoursSinceBooking <= 24 &&
  daysUntilDeparture >= 7;

return { freeCancellation: eligible };
```

Website: a booking made tomorrow for a flight in three days still appears eligible.

The API would decline a request the website appears to allow.

### Operations: A customer asks for help

Reference: Customer care / Example conversation

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

- Agent sees: Not eligible: departure within seven days

Fare rules and booking logic agree. The website does not mention the restriction.

The support team inherits the unresolved difference.

### Finding: Cancellation condition missing from website

The website omits a departure condition used in fare rules and booking logic.

- Website: free cancellation within 24 hours
- Fare rule: booking at least seven days before departure
- API: both conditions required

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

## Ship Management: scenario

A customer instruction reaches the vessel manager. Does the same instruction reach finance and the accounting system?

### Customer instruction: A new instruction arrives

Reference: Customer email / Vessel manager

From next month, please post maintenance expenses for Vessel North to account 6105, Vessel maintenance.



Service mapping: maintenance expenses still use account 6000, General operating expenses.

The customer instruction has not reached the posting rules.

### Standing order: Vessel North accounting instructions

Reference: Customer agreement / Standing order

Maintenance expenses must use account 6105. Apply this instruction to invoices posted from the start of next month.



ERP account setup supports 6105, but the service still selects 6000.

An agreed rule exists outside the operational configuration.

### Service layer: Expense account mapping

Reference: Example service / posting-rules.ts

The service assigns an account before sending the posting to the ERP.



```typescript
const accountByExpense = {
  maintenance: '6000',
  fuel: '6200',
};

postInvoice({ account: accountByExpense[type] });
```

Customer standing order: maintenance must use account 6105.

The mapping still points to the old general account.

### ERP configuration: Available posting accounts

Reference: ERP setup / Dynamics 365-style example

The account exists. The ERP accepts the account supplied by the service.

- 6105: Vessel maintenance / Active
- 6000: General operating expenses / Active
- Account selection: Provided by expense service

The customer requested 6105. The service supplies 6000, which is also valid.

A technically valid posting can still break the customer's rule.

### Finance posting: Invoice ready for reconciliation

Reference: Finance / Example ledger entry

A maintenance invoice has been posted to the general account.

- Vessel: Vessel North
- Expense: Maintenance
- Posted account: 6000 / General operating expenses
- Agreed account: 6105 / Vessel maintenance

The standing order specifies 6105 for this vessel and expense type.

Finance must reclassify the expense and investigate the mapping.

### Finding: Customer instruction differs from expense mapping

The standing order specifies account 6105 while the service still selects 6000.

- Customer email: use maintenance account 6105
- Standing order: effective next month
- Service mapping: maintenance uses 6000

Valid ERP postings can still require manual reclassification.

## FMCG: scenario

Three divisions share an ERP. Their service rules differ for good reasons. A shared default can erase those differences.

### Divisions: One group. Different commitments.

Reference: Example group / Customer delivery commitments

Each division serves a different customer need.

- Grocery: At least 5 days remaining
- Foodservice: At least 2 days remaining
- Processing: At least 1 day remaining

Dispatch service: a shared two-day default is currently used for every division.

Different thresholds are intentional. Applying one threshold everywhere is not.

### Policy: Grocery dispatch standard

Reference: Grocery division / Customer agreement

Products dispatched to grocery customers must have at least five days of remaining shelf life on delivery.



Foodservice requires two days and processing one day. These are separate agreed rules.

The grocery rule must retain its division scope.

### Service layer: Dispatch eligibility

Reference: Example service / shelf-life.ts

A common default has replaced the division-specific check.



```typescript
const minimumDays = 2;

return remainingDays >= minimumDays;

// Intended: look up the agreed
// threshold for this division.
```

Grocery policy: minimum five days. The shared default accepts two.

An order can pass the service check and still fail the customer agreement.

### Shared ERP: A common operational core

Reference: ERP / Dynamics 365-style example

The ERP records batches and dates. The service layer applies the division's delivery rule.

- Batch: LOT-042 / Example data
- Remaining shelf life: 3 days
- Destination division: Grocery
- Service response: Eligible for dispatch

Three days passes the shared default but falls short of grocery's five-day commitment.

The ERP data is consistent. The decision rule is wrong for this division.

### Operations: A planner reviews the order

Reference: Dispatch planning / Example conversation

This grocery shipment passed the check, but only has three days remaining. Which rule was applied?

- Service threshold: 2 days
- Grocery agreement: 5 days

The same batch could meet the other divisions' thresholds, but not this customer's.

Review the division mapping before releasing the shipment.

### Finding: Shared shelf-life default overrides grocery rule

A two-day service default is applied to grocery orders that require five days.

- Grocery agreement: five days
- Foodservice: two days / Processing: one day
- Service: two-day default for all divisions

A shipment can pass a system check while missing its division's customer commitment.
