ShopifyProvider sign-in; advanced key fallback
Connector availableSet up, connect and operate Idovio Commerce without guessing. This guide follows the same capability boundaries the application and its AI use.
Use the simplest supported authorization path. Idovio handles provider-specific details; advanced credentials remain a fallback where needed.
If the status is pending approval or E2E verification, the provider must not be presented as ready to connect.
Create the workspace around the way you actually sell and reach first value without enabling unnecessary modules.
Sign in, create or select a workspace and choose the business modes that apply to you.
Connect the minimum commerce loop: at least one sales channel and the supplier, warehouse or fulfillment source you actually use.
Confirm currency, time zone, permissions and the first safe synchronization before enabling automatic writes.
Use the Connection Hub as the single place to connect, verify, reauthorize and disconnect external services.
Prefer Connect → provider sign-in → authorization whenever OAuth or provider-hosted authorization is available.
If a provider requires an API key, use the guided advanced flow, grant only the requested scopes and let Idovio validate the credential.
Treat Connected as a real state: authorization, required scopes, health check and initial synchronization must all succeed.
Bring orders, catalog and channel state into Commerce without treating every marketplace as a separate operating system.
Connect each store or marketplace from Connections and review the capabilities granted by that provider.
Run the first read synchronization before enabling listings, price writes or other mutations.
Use Reconnect when authorization expires; do not create duplicate connections to work around an expired token.
Connect the sources that can actually fulfill your products and keep provider status separate from product sourcing policy.
Connect suppliers, POD partners or your own warehouse and verify cost, stock and delivery data before routing orders.
Use Supplier Router policies to compare eligible sources by landed cost, margin, availability, reliability and delivery limits.
Never enable automatic purchasing for a provider until its order flow and cost checks are verified end to end.
Keep product identity, offers and stock understandable across channels and fulfillment sources.
Map each product/SKU to the relevant channel listing and eligible supply sources.
Use inventory locations and movement history as the operational stock record; investigate mismatches instead of overwriting them blindly.
Configure low-stock and margin protection rules before allowing automatic routing or pricing changes.
Follow an order from channel ingestion to fulfillment while surfacing the cases that need a person.
Review payment/channel evidence and routing before the first automatic fulfillment action.
Use idempotent actions and the order history so retries cannot create duplicate supplier orders or labels.
Track shipment, cancellation, returns and exceptions from the same order context instead of reconciling separate dashboards manually.
Understand contribution margin, settlements and liquidity without mixing currencies or pretending estimates are confirmed money movements.
Review product cost, shipping, payment fees, marketplace fees and reserves before trusting a margin figure.
Import or synchronize settlement data to reconcile estimated fees with actual payouts where the provider permits it.
Use Cashflow/Liquidity views for operational decisions; do not treat them as a tax return or regulated accounting advice.
Automations do repeatable work; Guards define the boundaries that must not be crossed.
Start important workflows in simulation or approval mode and inspect the generated actions before enabling automatic execution.
Configure hard limits such as minimum margin, price-change bounds, order value, spend or supplier constraints.
Use history, idempotency and Emergency Stop to understand and stop automated behavior without deleting the underlying configuration.
Work the problems first instead of manually checking everything that is healthy.
Use the Exception Center to find failed syncs, authorization problems, stock risk, margin blocks, supplier failures and financial mismatches.
Open the evidence attached to the exception before taking a corrective action.
Resolve or safely retry the underlying problem; do not hide a recurring exception without understanding its cause.
AI is optional. Commerce remains the authority for data, permissions and execution.
Connect a supported AI provider with account linking when available or use the guided API-key method.
Choose Advisor, Assistant, Operator or Autonomous separately from the provider/model you selected.
Even in Autonomous mode, actions pass through Tool Registry, RBAC, workspace policy, Guards, approvals, audit and workers. Use Emergency Stop whenever you want to suspend delegated AI actions.
Give people and connected services only the access they need for their role.
Use named accounts, MFA where available and role-based permissions instead of shared administrator access.
Review connector scopes and AI permissions after team, provider or workflow changes.
Never paste API secrets, recovery codes or provider credentials into chat, support tickets or ordinary notes.
Diagnose connection and workflow problems from evidence before reconnecting, deleting or recreating data.
Check connection health, required scopes, last successful sync and the relevant Exception/Automation history.
If authorization expired, use Reconnect and repeat provider consent instead of creating a second integration.
If the problem persists, record the workspace, provider, affected entity and approximate time, then contact support without sending secrets.
Keep the workspace, provider and approximate time of the issue ready. Never send passwords, API secrets or recovery codes to support.