Which store functions can a Digital FTE own?
Three. Product and category content: a Search Visibility or Content FTE answers the questions shoppers actually search for about your products from your product data, with every claim through the fact gate, and publishes to Shopify through its own API on approval. Order support: a Customer Support FTE resolves order-status, shipping, and how-to tickets from the order record and the knowledge base with a citation, while refunds, returns disputes, and chargebacks reach your team. Payout reconciliation: a Finance Controller FTE matches processor payouts to orders net of fees every morning, with the fee schedule attached.
None of them changes a price, issues a refund, or edits a product without approval.
What should an e-commerce director ask?
Ask how it publishes to the store: through the platform's own API, as a draft or a live product page according to the connection's permissions, appearing in your admin where your own workflow can add a check. Ask what a payout match shows: the payout, the orders it covers, and the fee schedule that explains the difference, with the FTE proposing rather than posting. Ask what a support ticket can and cannot do: read the order record and answer status and how-to questions; never issue a refund, change an address after dispatch, or handle a chargeback.
Ask what happens during a surge: per-role budgets bound the spend, the wallet stops at zero, and every escalation still reaches a person with a summary.
- Publishing: Shopify API, draft or live per permissions?
- Payouts: orders and fee schedule attached, proposed not posted?
- Support: order record read, refunds and chargebacks human?
- Surge: budgets bound spend, escalations still reach people?
What should an e-commerce director measure?
For content, product pages published that passed the fact gate, citation and console movement for the product questions in the prompt set, and cost per page against what a page cost before. For support, first-line resolution for order-status and how-to categories, median first response including overnight, and escalation quality; measure it through a peak, because that is when it matters. For finance, payouts reconciled daily, exceptions open on day one of the close, and days to close.
Refuse to measure conversion as a target of the content FTE; it can earn visibility, and the store's conversion has causes it cannot see. The performance view will mark it unmeasured.
What should an e-commerce director refuse?
Refuse any product claim without a source in your product data; the fact gate blocks it, and you should never add a source afterwards. Refuse to let the support FTE touch refunds, address changes after dispatch, or chargebacks at any level. Refuse to promote payout matching beyond exact matches under a threshold. Refuse to start all three functions at once; start with the one whose evidence is clearest, usually payouts or order-status support. And refuse to go into a peak without per-role budgets set.
The refusals keep a busy season from becoming an incident.
How does a peak season work with Digital FTEs?
Before the peak, set the per-role budgets and the always-escalate receivers for the volume you expect, confirm the knowledge base articles for order-status and returns are current, and promote nothing. During the peak, the support FTE's first line absorbs the order-status surge with cited replies while your team handles the escalations that arrive with summaries; the finance FTE reconciles the larger payouts daily so the post-peak close is not a reconstruction. After the peak, read the escalation reasons; they are next year's knowledge base and remit fixes.
The planning guide for peak support in the library is the week-by-week version.
What do the first 30 days look like from the e-commerce director's seat?
Week one: choose payouts or order-status support, connect Shopify and the processor or the helpdesk with scoped credentials, write the remit with the escalate list and receivers, and record the baseline. Weeks two to four: approve evidenced matches or cited replies in minutes a morning, send back with reasons, read the reasons weekly. Day 30: read the FTE's own report, decide whether exact matches or the one support category has earned promotion within bounds, and choose the second function.
By day 30 one store function has an owner that works every morning, and the second is set up in a fraction of the time because the platform already knows the store.
What does the platform not do for an e-commerce director?
It does not set prices, run promotions, or change inventory. It does not issue refunds or handle chargebacks. It does not promise conversion. It does not publish a product claim without a source. And it does not measure what the store's own data cannot show; it says unmeasured.
An e-commerce director who wants a store that runs itself should look elsewhere. One who wants product content that passes a gate, order support that answers from the record, and payouts reconciled daily, each approved and logged, has the mechanisms here.