Hybris asks OIX for the courier nickname when a parent order completes, then posts the paid tip back to OIX. OIX decides whether that record belongs in the database or the error stream — and if it belongs, which system actually pays the courier.
Sixteen steps across four phases. Click any node for its rules, inputs and failure behaviour.
Flip each rule and watch the verdict change. Passing records fall through to the assignment engine.
For any reason the record cannot be processed, it must not be written.
No unique code means duplicates cannot be caught — reject it.
Order number must resolve in OIX, add-on numbers to their parent.
Hybris returning 0 or a negative amount is a rejection, not a free tip.
Properly formatted and plausible — malformed or unexpected values are rejected.
All five conditions pass. The record is written and the assignment engine takes over.
Assigned. Tip is 100% to the courier but counts toward salary, so MPF and tax apply.
One prefix decides the destination, the payment mechanism and the reporting cadence.
Every record from the past 7 days where assignee = null. The follow-up queue for tips that could not be attributed.
All records of the month where assignee ≠ null and starts with LF or LP. This is the payout list for the salary run.
ODS tips travel in the independent report attached to the regular approval email. SAP receives the records the same day, after the send.
Configurable interval. When new tips exist, the app pops a notification with customer name, amount and payment time.
Today, past 7 days and this month — plus a past-7-days breakdown on the courier side.
100% of the tip goes to the courier, but it is counted toward salary: MPF and tax apply.
Housekeeping is undefined. Technical team monitors volume and archives when needed; otherwise records stay live forever.
One field on SSO with no language constraints. That is expected, not an omission.