Feature request: official Shopee connector/plugin for Codex ecommerce workflows

Summary

Please consider supporting an official Shopee connector/plugin for Codex so Shopee sellers, operators, and ecommerce developers can use Codex with authorized Shopee API workflows instead of manual copy-paste, browser scraping, unofficial automation, or credential sharing.

Shopee is one of the largest ecommerce marketplaces in Southeast Asia. A native connector would make Codex significantly more useful for real seller operations while creating a safer, permissioned integration path.

Problem

Many marketplace sellers already use AI tools for repetitive operational work, including product listing drafts, SKU cleanup, inventory planning, order summaries, customer reply drafts, and sales reporting.

Without an official connector, users may fall back to risky patterns:

• copying sensitive order/customer data into external tools manually
• using unofficial scripts or browser automation
• sharing seller credentials with third-party tools
• losing auditability for changes to listings, stock, prices, campaigns, or customer messages
• lacking clear permission boundaries between read-only analysis and write actions

Proposed integration

Expose selected Shopee Open Platform capabilities as structured Codex tools with clear permission scopes, explicit user confirmation, and auditability.

A practical architecture could include:

• OAuth-based Shopee seller authorization
• store-level permission scopes
• separate read-only and write-enabled modes
• revocable access from the seller account
• API rate-limit compliance
• least-privilege handling of customer/order data
• confirmation gates before sensitive write actions
• audit logs for seller-visible changes

Suggested capabilities

Product and catalog workflows

• Read, create, and update product listings
• Validate categories, attributes, variants, images, price, stock, and description completeness
• Generate draft listings that require seller approval before publishing
• Detect missing attributes, weak product titles, inconsistent SKU data, and listing quality issues

Order and fulfillment workflows

• Retrieve order status, shipment status, cancellation status, return/refund cases, and fulfillment deadlines
• Summarize operational risks such as late shipment, unresolved disputes, repeated refund reasons, and fulfillment exceptions
• Prepare draft operational actions while requiring explicit seller confirmation before any write operation

Customer service workflows

• Draft customer replies using order, payment, shipment, and return/refund context
• Summarize buyer complaints and recurring support issues
• Help sellers respond faster while keeping final message sending under seller control

Reporting and analytics

• Retrieve sales, SKU, inventory, promotion, conversion, cancellation, and return/refund data
• Generate seller reports, trend summaries, and exception alerts
• Identify low-stock risk, high return rates, delayed fulfillment, underperforming listings, and campaign issues

Why this matters for Codex

A Shopee connector would expand Codex from code assistance into practical ecommerce operations, especially for sellers and developers in Southeast Asia.

Benefits:

• improves Codex usefulness for marketplace sellers and ecommerce developers
• enables safe AI-assisted store operations through structured tools
• reduces unsafe workarounds such as scraping, shared credentials, and manual copying of sensitive data
• creates a reusable pattern for future marketplace connectors
• supports a fast-growing ecommerce user base in Southeast Asia
• preserves user control through explicit authorization, confirmation, and audit logs

Safer MVP

A first version could be read-only plus draft-generation only:

• seller analytics summaries
• inventory and SKU diagnostics
• listing validation
• order and fulfillment summaries
• return/refund issue summaries
• draft customer replies
• draft listing improvements

Write actions such as publishing listings, changing prices, changing stock, editing campaigns, or sending buyer messages could be added later with stronger confirmation and logging requirements.

Routing request

If this repository is not the right place for connector/plugin ecosystem requests, could the maintainers please route this to the appropriate Codex apps/connectors, developer partnerships, or platform integrations team?