What changed: a merchant workspace within an office assistant

Qwen Work introduced its ecommerce edition on October 14, 2026. The desktop client's version 1.3.1 update on October 15 then listed “ecommerce mode.” Users can switch between everyday office work and ecommerce operations, managing conversations, projects and scheduled tasks separately and using related connectors and an operations dashboard. See the product update and client changelog.

A connector lets the assistant access an external platform, account or tool. This announcement includes a Taobao and Tmall merchant connector, with merchant scenarios such as data analysis, product selling-point analysis and creative assets. The official material also states that ecommerce access is limited to personal accounts, is not yet available to enterprise accounts, and remains invitation-only.

Why it helps: keep store questions with the relevant tasks and material

A small shop may be preparing a hiring notice while organizing a product campaign. When every conversation and scheduled task sits together, finding which sales sheet a campaign used can require searching through unrelated work. Ecommerce mode provides a place to manage store tasks while ordinary office work stays in the other mode.

A suggested starting point is one small task: use a week's product data to identify changes worth checking, then draft a description for one item. The desired output is a draft with a clear period and evidence, rather than a vague statement that advertising performed well. Even with a platform connected, check the store, dates and field definitions. Data from different stores or based on different definitions should not be combined without care.

How to start: confirm access, then review a small set of data

Download or update the desktop client from the Qwen Work website and sign in. Confirm that your personal account has an invitation, then look for ecommerce mode in the account. If the entry is absent, check the invitation notice; installing a connector does not automatically grant access. The following task uses the desktop client and a local spreadsheet, without first connecting a merchant platform.

  1. Prepare an identifiable file. Switch to ecommerce mode and choose one store, one date range and one question. Put an authorized sales file in a clear local location and note its full path—for example, shop-week.csv inside a “Store review” folder on the desktop. The official introduction confirms direct access to local spreadsheets in the desktop client.
  2. Identify the file and confirm what was read. Following the desktop guide, select New task in the sidebar and describe the request. Start with a suggested prompt: “Read this file: [replace with the actual full path]. First list the file name, worksheets or column names, and the data's date range. Do not calculate yet or modify the original.” The official file-task examples also specify local directories in instructions. Compare the recognized content with your file and inspect the files used in Task Monitor. Correct a missing path or wrong sheet before continuing.
  3. Request a bounded, checkable analysis. Once the file and dates are confirmed, continue in the same conversation: “Analyze only last week's data in this file. List sales value and changes by product, with the calculation basis. Say if a comparison period is missing. Do not change advertising settings.” This is a suggested prompt. Without previous-period data, ask for current-period results and the missing inputs, not a guess.
  4. Check the output, then work on copy. Open the returned file or analysis and check the store, dates and two or three calculations. Request changes in the same conversation if needed, then draft copy using confirmed product information. Decide whether to schedule recurring work only after obtaining a useful draft.

For external merchant data, separately check the connectors available in your account and their authorization scope. The “Extensions → install → My installations/Add resources” path in the extension guide is documented for the web app; it is not the operating path for the desktop file task above. Analysis still needs checking and does not mean a store action has been executed.