Notes from Marketplace Integrations Discussion (APAC)

Informal opening with weather chatter (wind, rain, alternating sunny and rainy days); perceived as a casual start to the meeting.
Participants referenced in the transcript include Barrianda, Paolivina, Deepak, Mariana, and others (e.g., Kapiti, Paiyuparaj). The exact roles are not fully clarified in the excerpt.
Purpose stated early: discuss integration to marketplaces and a centralized system to handle customer inquiries across channels (WhatsApp, web chat, marketplaces, etc.).

Primary objective discussed: evaluate integration of marketplaces into a centralized omnichannel system with AI/chat automation.
Decision conveyed: for the moment, we are not proceeding with marketplace integration.
Rationale: need a centralized system to handle customer inquiries from multiple channels (WhatsApp, web chat, marketplaces) in one place; current setup does not meet this requirement.
Acknowledgment of this decision and intent to revisit in the future when conditions align.

Marketplaces discussed as potential integration targets in APAC with public chat APIs: Lazada, Shopee, Tokopedia, and DB (name unclear; could be Bukalapak or similar).
The team noted that not all marketplaces have public chat APIs; this impacts integration feasibility.
Specific mentions:
- Lazada: considered for integration; has public APIs for chats (subject to availability and authorization).
- Shopee: debate about automation vs agent chat; policy is a concern.
- Tokopedia (Toepokida/Tocopedia in transcript): mentioned as part of the APAC set; automation is referenced for some channels.
- DB: mentioned as part of the APAC set; API availability uncertain.
A vendor-related request to confirm which marketplaces can be connected and the corresponding API status.
There was a note about another marketplace (Beebe/Beebe-like) where API availability is uncertain; if available, integration could be explored.

Core requirement: integrate chats across all APAC marketplaces with public chat APIs when available.
Deepak/Team stance: for some marketplaces, integrations are already in place as part of an omnichannel inbox; for others (e.g., Beebe), open/public APIs may not be available yet.
For four APAC marketplaces (Tokopedia, Shopee, Lazada, DB): there are “ready-made integrations” in place for the omnichannel inbox, with caveats about API availability and marketplace policy.
Automation capabilities:
- Lazada and Tokopedia: automation layer exists to automatically respond.
- Shopee: the only feasible approach discussed is agent-driven chat (manual live agent), with concerns about automation due to marketplace policy.
- There was disagreement on Shopee automation: one side claimed automation is possible; the other highlighted policy risk (APIs restricting automation, risk of account blacklisting).
General implication: while automation for some marketplaces is feasible, Shopee’s policy creates uncertainty and risk; this affects the overall feasibility of a unified automation solution across all target marketplaces.

Deepak stated that, apart from Beebe, there are already integrations in place for the four marketplaces; if Beebe has open APIs, those could be explored as well.
Beebe’s API status remains uncertain; no firm timeline provided.
The existing setup is described as an omnichannel inbox with integrations ready for Lazada, Tokopedia, Shopee, and DB (subject to API availability and marketplace policies).
For Shopee specifically, there is tension between automation capabilities and policy restrictions; one party suggested automation is possible, while another warned of potential blacklisting if automating against policy.

Technical constraint: not all marketplaces provide public chat APIs; this directly limits integration scope and feasibility of a single centralized system across all channels.
Policy constraint: Shopee’s API policy may restrict automation; engaging in automation could risk account blacklisting, which has ethical and business risk implications.
Practical implication: even though some marketplaces (e.g., Lazada, Tokopedia) have automation-ready APIs, the overarching goal of a single centralized system remains contingent on policy-compliant access across all target marketplaces.
Decision constraint: the team decided to pause and not engage Geoharthic (the vendor discussed) at this time, pending clearer alignment on API access, automation policy, and potential timelines.

Acknowledge and document the decision to pause marketplace integration for now.
Plan to revisit the integration once conditions improve (e.g., broader API access across marketplaces, clearer automation policies, or a centralized requirement alignment).
You will evaluate other vendors and vendor capabilities, and only proceed if a centralized, policy-compliant solution can be achieved.
Confirm and circulate the Minutes of Meeting (MOM) to all participants.
Maintain openness to re-engage with vendors to activate discussions when appropriate.

Which marketplaces will be targeted for initial integration if we resume the project (Tokopedia, Lazada, Shopee, DB, Beebe)?
Are there official API access programs or partner programs that could ease integration across all APAC marketplaces?
Can we design a centralized system that accommodates live agent chats where automation is not allowed (Shopee) while enabling automated responses on marketplaces that permit it (Lazada, Tokopedia)?
What is the realistic timeline and resource requirement to implement an omnichannel inbox with cross-marketplace automation, given API availability and policy constraints?
How do we handle risk management and vendor relationships when automation could potentially violate marketplace policies?