[RELEASES ON 17th June 2026]

Overview

Grubtech now supports the capture and persistence of customer tax profile data as part of the inbound order payload. This feature enables aggregator platforms that collect tax identification at checkout to pass that information through to Grubtech, where it is stored against the order record for downstream use.

This closes a gap in the current customer data model, which previously supported only name, contactNumber, and email. Tax profile data is increasingly required by merchants operating in VAT-regulated markets, and this feature ensures that information is not lost at the integration boundary.

What's changing

A new optional taxProfile sub-object is now accepted under customer in the POST /orders Order Notification body.

Field	Type	Description
`customer.taxProfile.taxId`	string, optional	Customer's tax registration number
`customer.taxProfile.taxName`	string, optional	Customer's registered tax name
`customer.taxProfile.email`	string, optional	Tax-associated email, distinct from `customer.email`

When present, these values are persisted to customerDetails.taxProfile in the Grubtech order document.

Example

Request — POST /orders

{
  "customer": {
    "name": "Acme Corp",
    "contactNumber": "+971501234567",
    "email": "[email protected]",
    "taxProfile": {
      "taxId": "TX-98765",
      "taxName": "Acme Corporation LLC",
      "email": "[email protected]"
    }
  }
}

Behaviour and edge cases

Scenario	Outcome
`taxProfile` with all three fields provided	All values persisted as-is
`taxProfile` with a subset of fields (e.g. `taxId` only)	Provided fields persisted; missing fields stored as `null`
`taxProfile` absent from payload	Order processes normally; `customerDetails.taxProfile` stored as `null`

Integration impact

This is a fully additive, non-breaking change.

No changes are required to your existing integration.
Adoption is optional — only include taxProfile if your platform captures this data.
No API version bump. The existing POST /orders endpoint contract is extended in place.

Availability

Environment	Status
Staging	Live — available for testing now
Production	17 June 2026

Next steps for integration partners

Update your order payload to include customer.taxProfile where applicable.
Test against the staging environment and validate persistence using your preferred order inspection method.
Raise any issues or questions with your Grubtech integration contact ahead of the production cutover.