tw-ecom-dtc-91app

asgard-ai-platform ｜ 商業與營運 ｜ 原文 ｜ MIT

透過 mcp-91app 串接 91APP，處理 OMO 與會員同步（內文待補）

---
name: "tw-ecom-dtc-91app"
description: "透過 mcp-91app，在台灣電商情境下串接並營運 91APP。當要在 91APP 上同步訂單/商品/會員、執行 OMO（online-merge-offline）流程、整合 91APP 以 app 為主的店面，或比較 91APP 與 Shopline/Shopify 用於中型 DTC 時使用。Shopline 專屬的串接「不要」用這個（看 tw-ecom-dtc-shopline）。STATUS: SKELETON — 內文待補。"
metadata:
  category: "WP-01 電商"
  domain: "ecommerce-tw"
  layer: "platform"
  related_mcps: ["mcp-91app"]
  related_skills: ["tw-ecom-channel-strategy", "tw-ecom-dtc-shopline"]
  last_verified: "2026-04"
  status: "skeleton"
  tags: ["taiwan", "e-commerce", "91app", "platform", "integration"]
---

# 91APP 串接方法論

> **STATUS: SKELETON**：內文待補。

## 何時使用這個 skill

- 透過 mcp-91app 串接 91APP
- 執行 91APP 專屬的 OMO（online-merge-offline）流程
- 在 91APP 和 CRM 之間同步會員資料
- 除錯 91APP 的促銷 / 優惠券流程
- 比較 91APP 與 Shopline 在中型 DTC 區隔的差異

## 何時「不要」使用

- 需要一般的平台選擇指引 → 用 `tw-ecom-channel-strategy`
- 需要 91APP 的 API schema 文件 → 直接查 mcp-91app 的 README

## 核心概念

TODO: 91APP 以 app 為主的定位、OMO 模型、以會員為中心的架構。

## 決策樹

TODO: 哪個任務該用 mcp-91app 的哪個 tool。

## 實作指引

TODO: 訂單同步、會員同步、促銷設定、庫存同步流程。

## 常見陷阱

TODO: 5-6 個陷阱（候選：OMO 狀態漂移、促銷疊加規則、跨網頁/app 的會員合併、配額上限）。

## IRON LAW

TODO: 一個不明顯的限制。

## 輸出格式

TODO.

## 相關

- `tw-ecom-channel-strategy`
- `tw-ecom-dtc-shopline`（方法論範本）

_Last verified: 2026-04_

---
name: "tw-ecom-dtc-91app"
description: "Integrate and operate 91APP in Taiwan e-commerce context via mcp-91app. Use when syncing orders/products/members on 91APP, running OMO (online-merge-offline) flows, integrating 91APP's app-first storefronts, or comparing 91APP vs Shopline/Shopify for mid-market DTC. Do NOT use for Shopline-specific integration (see tw-ecom-dtc-shopline). STATUS: SKELETON — body pending."
metadata:
  category: "WP-01 電商"
  domain: "ecommerce-tw"
  layer: "platform"
  related_mcps: ["mcp-91app"]
  related_skills: ["tw-ecom-channel-strategy", "tw-ecom-dtc-shopline"]
  last_verified: "2026-04"
  status: "skeleton"
  tags: ["taiwan", "e-commerce", "91app", "platform", "integration"]
---

# 91APP Integration Methodology

> **STATUS: SKELETON** — body pending.

## When to use this skill

- Integrating with 91APP via mcp-91app
- Running OMO (online-merge-offline) flows specific to 91APP
- Syncing member data between 91APP and CRM
- Debugging 91APP promotion / coupon flows
- Comparing 91APP vs Shopline for the mid-market DTC segment

## Do NOT use when

- You need generic platform selection guidance → use `tw-ecom-channel-strategy`
- You need 91APP API schema docs → consult mcp-91app README directly

## Core concepts

TODO: 91APP app-first positioning, OMO model, member-centric architecture.

## Decision tree

TODO: which mcp-91app tool for which task.

## Implementation guidance

TODO: order sync, member sync, promotion setup, inventory sync flows.

## Gotchas

TODO: 5-6 pitfalls (candidates: OMO state drift, promotion stacking rules, member merge across web/app, quota limits).

## IRON LAW

TODO: one non-obvious constraint.

## Output Format

TODO.

## Related

- `tw-ecom-channel-strategy`
- `tw-ecom-dtc-shopline` (methodology template)

_Last verified: 2026-04_