What does a Marketplace FTE own?
A Marketplace FTE on ftes.ai owns a store's marketplace presence as a job function rather than as a set of dashboards someone checks when sales dip. That means the health of every listing on Amazon, Walmart, eBay and Etsy, the Buy Box and the price position on each, sponsored advertising inside a budget, the reviews and questions customers leave, and the inventory the marketplaces believe the store has. It is accountable for one outcome, marketplace revenue at a margin the owner can see with every change approved, and it is reviewed on targets such as suppressed listings recovered within a day and margin after fees per SKU.
It does not own pricing strategy, product selection or the decision to enter or leave a marketplace. The owner decides those. The Marketplace FTE runs the channel inside the floors, caps and rules the owner writes, and reports numbers it measured.
How does it handle suppressed and degraded listings?
Every morning the Marketplace FTE reads each marketplace's listing health reports and finds listings that are suppressed, meaning hidden from search until a problem is fixed, or degraded, meaning visible but missing something the marketplace rewards. For each it names the exact field that failed, such as a main image that does not meet the background rule, an empty bullet field, a title over the length limit, or a missing attribute for the category, and drafts the fix from the store's product data, never from invention.
The fix is a proposal in Approvals with the suppression notice, the before-and-after listing and the check it passed. Because a suppressed listing earns nothing for every hour it is down, suppression fixes are the class of change most owners promote to run without a gate first, once the approval record is clean.
How does it watch the Buy Box and prices?
The Marketplace FTE monitors, for every SKU, whether the store holds the featured offer, the Buy Box on Amazon and its equivalents elsewhere, and what changed when it does not: a competing offer's price, fulfillment method, stock, or the store's own seller metrics. It reports the change in the morning brief with the evidence, and where a price move would recover the position it proposes one, inside the price floor the owner set for that SKU.
The price floor is a hard limit above the autonomy ladder. The FTE cannot propose, let alone make, a price below it. A SKU where the Buy Box cannot be held above the floor is reported as such, with the margin arithmetic, so the owner can decide whether to compete or to let it go.
How are sponsored ads run inside caps?
Sponsored advertising on a marketplace is run by the Marketplace FTE inside a daily or monthly cap per marketplace that it cannot exceed. Within the cap it proposes bid changes, keyword additions and removals, and new campaigns, each with the evidence: the search terms that converted, the terms that spent without converting, the margin after fees of the SKU being advertised. At Level 0 every change waits in Approvals; routine bid adjustments inside a range can be promoted later.
It reports advertising cost against the cap and against the margin it produced, per SKU, so an ad that sells a product at a loss after fees is visible as a loss, not as sales.
What about reviews, questions and inventory?
Customer reviews and questions on a marketplace are drafted by the Marketplace FTE in the store's voice, from product data and approved copy, and wait for approval before they post. Anything that touches safety, a legal claim or a request for a refund is escalated to a person rather than answered. Inventory is synced from the store's stock so that a sale on the store reduces what the marketplace offers, and a stock level that would oversell is flagged before it does.
Where the store also employs an Inventory FTE, the Marketplace FTE reads its stockout risk before proposing an ad bid on a SKU that is about to run out, which is the kind of coordination that separates a department from a set of tools.
How does it report margin honestly?
The Marketplace FTE reports margin after fees per SKU and per marketplace: the sale price less the referral fee, the fulfillment fee where the marketplace fulfills, storage where it applies, advertising attributed to the SKU, and the landed cost the owner supplied. The number is stated with its inputs, so the owner can challenge any of them. A SKU that sells well and loses money after fees is named, with the arithmetic, and the FTE proposes what to do: raise the price inside demand, change the fulfillment method, or stop advertising it.
It does not report gross marketplace sales as the headline, because gross sales are the number that hides the loss.
Which tools does it work in, and why is onboarding custom?
The Marketplace FTE works inside Amazon Seller Central and Amazon Ads, Walmart Marketplace, eBay and Etsy with the permissions the owner grants per account, and reads stock and orders from the store platform. Onboarding is custom: the marketplace permissions, the landed-cost sheet that makes margin real, the price floors per SKU and the ads caps are agreed with the ftes.ai team before the role starts, because a marketplace channel run on wrong inputs produces confident wrong numbers.
Credentials are encrypted at rest and revocable, the work is reviewed in the ftes.ai workspace, and the role draws tokens from the organization wallet with a hard stop at zero.