Labels depends on a booking existing? Use the booking id as the root identifier for labels? Use api standardisation Flags vs status "IsReady":true vs "Status":"Ready" Raise webhooks, sockets and events.

Create a new homepage app which would be multi-tenanted, multi-language and muilti-currency. Standardise locale cookies so they can be used server side, client side and on the router. Implement new locale cookies in legacy solution (move away from languageid implementation) Use existing order process on the existing url (parcel2go.com/order). Cookies would be used to determine locale & currency (website). Allow multiple different redirection schemes (so whitelabel are not locked to how we do things). If there are SEO pages which we want to make multi-locale then they would have to be routed (either app router or asp routing) or migrated to react. Anything which uses the legacy solution will be slow due to hosting in Ireland limitations. new order process will fix this