What's new in POT v1.9.0?
Demand Changes
- Item Menu Grouping
- New Booking Status
VOUCHER_PENDING
- New
contentSource attribute -> this attribute was added to help Demand in developing the Translated by Google watermark on Product Detail & Item Detail
- New Online attribute -> this is to enable Online Xperience through POT
- Adding Provider Detail on Booking Details API -> this is to support customer ops that requires detail information of the provider e.g Axes, BMG, or Viator.
- New Event: Product Chain Deactivation
Refer to: https://docs.google.com/document/d/1obzSagrYYDgaYAQGj0TJKpk_xtioQi-OK3ThortBHOw/edit?usp=sharing
POT Modules
Aggregator Management
- New Job Import UI -> MP can now whitelist products from providers by themself by inputing the desired product IDs
Payment Management
- Show RESERVED status on Booking Manifest -> showing this status will help both Engineers, PMs or other Operation team when checking the status of a particular booking.
Product & Item Management
Major update on Product & Item Management is the canonicalization logic. Canonical logic needs to be changed due to unexpected grouping occurred during migration. Here are the new criteria:
- Addition of Provider as the first check. If Provider is different, then the product will be considered for similarity comparison
- Increase name similarity requirement to 100% match
- Geolocation proximity is within 10 meters
Other releases includes
- New Resolution Required tab -> this tab will list down all products that has been imported but requires manual intervention to decide whether it's similar to another product group or not. This list would potentially be populated once we on-board more providers with overlapping products e.g. BMG & JTR
- New Product Resolution page -> this page is intended for BOI / MP team to select where should a product from a specific provide being grouped to
Refer to: https://zpl.io/VkePGRZ
Content Management
- Partial Content Task -> You can now create content task only for the required part, either it's Product content, item content or just images. This will help improve efficiency on handling content updates (either pushed by system or manually by Content Editor) but still maintaining control of content. Try it out!
Refer to: https://zpl.io/bJJKNp9
Other Supporting Dev
- AFB flow: translate content if it's non-EN to EN. Translation will be done using Google Translate.