Catalog answers
Proposed product descriptions and public store policies would help answer questions before purchase.
Integrations Ecwid
EcwidPlanned
Ecwid orders, in the support conversation.
Bring storefront questions and verified Ecwid order context together in a planned Message connector.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Commerce
What we’re planning to connect.
- 01Ecwid
- 02Planned connection
- 03Message support
Delivery questions
A proposed order lookup would show fulfillment context only after customer verification.
Multi-site selling
Keep each connected store tied to the correct workspace so a customer never sees another merchant’s order.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Public product descriptions
Verified order status
Store identifier
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose one Ecwid store and identify a public product plus a private test order.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test a wrong email, a wrong postal code and an order from another store before enabling order answers.
Before you connect
Ecwid integration questions
Can I connect Ecwid to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test a wrong email, a wrong postal code and an order from another store before enabling order answers.