Seller AutoBusiness

Hand an approved order to Steadfast as a real courier consignment. This books a pickup with a third-party courier and commits the merchant to a delivery attempt and its cost — cancelling means dealing with Steadfast directly, not undoing it here. Require an explicit go-ahead from the merchant for each order. Before calling: the order must be `approved` (see approve_order) and its delivery address complete — Steadfast builds the consignment from the address stored on the order, so a missing district or station becomes a failed delivery, not a validation error here.

Get a one-time link for the merchant to connect Steadfast. They open it, sign in again there, and paste their Steadfast API key and secret on that page — this tool never sees or asks for either value. The link expires in 30 minutes and works once. Tell the merchant to open it themselves; after they're done, confirm with get_steadfast_status rather than asking them to report back.

Delete a bundle offer permanently. For an offer the merchant might run again, update_bundle with is_active false is the reversible choice.

Delete a campaign. This does NOT retract anything already published to Facebook from it — those posts stay live on the Page and have to be removed there. Confirm with the merchant first.

Delete a comment from the Facebook Page permanently. There is no undo and no copy kept on Facebook's side — prefer set_comment_hidden for anything reversible, and reserve this for comments that should be gone outright (genuine spam, abuse, leaked information). Rate-limited to 10/hour per business, deliberately tighter than set_comment_hidden's 30/hour precisely because deletion can't be undone.

Remove a delivery option. Existing orders that used it keep their recorded delivery cost, but buyers can no longer choose it at checkout.

Permanently delete a detected order record. Intended for hallucinated detections with nothing behind them. If a real buyer really did back out, cancel_detected_order preserves the trail — prefer that.

Remove a discount. The product returns to its normal price on the storefront immediately.

Permanently delete an order record, restocking its items if it had been processed. This destroys the sales history for that order — for a real order the buyer walked away from, set_order_status 'cancelled' is almost always what the merchant actually wants. Reserve deletion for junk records (duplicates, test orders, orders an AI mis-detected) and confirm before calling. Owner-only.

Delete a product from the catalog. It disappears from the public storefront immediately. Confirm with the merchant first — setting stock to 0 via update_product hides it from buyers without destroying the record and its order history.

Delete a social post record from the app. If it was already published, this removes only the app's copy — the post stays live on Facebook and has to be deleted there separately.

Disconnect the Daraz account. Reconnecting needs the merchant to walk through Daraz's own browser consent screen again, which cannot be done from here — so confirm before calling.

Disconnect the Shopify store. Reconnecting needs Shopify's browser OAuth flow in the app — confirm before calling.

Read an old Facebook post and turn what it advertises into catalog products. This SPENDS LLM TOKENS — but the result is cached per post, so a second call on a post already marked completed returns the stored products instead of re-analysing. Check get_post_extraction_status first and never loop this across a whole feed without the merchant asking. Created products count against the plan's product limit. Extraction is disabled for posts the app itself published, to avoid duplicates. Review what comes back before treating it as catalog truth: prices and variations read out of marketing copy are frequently wrong.

Find the Messenger conversation for a given Facebook user id — the bridge from an order's sender_id or a comment author back to the chat thread.

Get how much of each metered feature is left this period: products, campaigns, Facebook posts, comment syncs, backup posts and AI replies. Check this BEFORE any action that consumes quota — upsert_products, create_campaign, sync_comments and the marketplace imports, plus every path that posts to the live Facebook Page (publish_social_post, schedule_social_post, publish_campaign_to_facebook, post_message_to_page, repost_backup_post — all five draw from the same monthly fb_posts allowance and share one hourly rate limit on top of it). What happens at zero differs by resource: upsert_products fails only the OVER-cap items and still creates the rest (read its response's `errors` array); create_campaign and the five Facebook-publish tools fail the whole call outright. Either way, once a monthly counter reads 0 remaining here, calling the tool anyway just wastes a round trip on a guaranteed failure — tell the merchant they've hit their plan's limit and need to upgrade in the Seller AutoBusiness app to do more this period, rather than retrying the same call. Plan name, subscription status, renewal date and billing details are deliberately NOT available here — if the merchant asks about their plan, pricing or subscription, tell them to open the app rather than guessing.

Read the Page's AI assistant mode — none, order placement, or full assistance. This governs whether the app is already replying to buyers automatically. Check it before proposing that the merchant reply to threads by hand, and before drafting replies the assistant may already have sent.

Get one bundle: its items, quantities, variation selections, pricing mode and final price.

Get the connected business: name, storefront slug and public storefront URL, shop type, currency, full address and coordinates, contact details, social links, branding (logo, cover, brand colours), checkout order policy, and the configured delivery options. Start here — most other tools read more usefully once you know the store's currency, category and whether a storefront slug is set.

Get one campaign in full: copy, time window, linked products and bundles, images, and status.

Read what the automation rules actually did — which comment, which rule, which action, and whether it succeeded. The place to look when a merchant asks why something was auto-replied to or hidden.

Read the messages in one Messenger conversation, newest first. Read the thread before drafting any reply — the buyer has usually already been told the price, the stock or the delivery time, and repeating it wrong costs the sale.

Get per-buyer summaries for the Page's conversations — order history and engagement, so a reply can be written knowing whether this is a repeat customer or a first contact.

Get the attributes Daraz requires for one category. Daraz rejects a listing that omits a required attribute, so check this before an export rather than debugging the rejection afterwards.

Check the Daraz connection: connected or not, the seller id, and whether the authorisation has expired. An expired connection is the usual cause of Daraz sync failures and can only be fixed by the merchant reconnecting in the app — Daraz's consent screen needs a real browser.

Get the detected orders for one conversation, as a timeline with the pricing breakdown and delivery details the AI extracted. Use this to check a detection against what the buyer actually wrote.

Check whether a Facebook Page is connected to this business, and which one. Read this before any other Facebook tool — everything else here returns an error, not an empty result, when no Page is connected. One Page per business today. Connecting a Page needs Meta's browser consent screen and cannot be done from here; send the merchant to the app's Facebook tab.

Get the connected Page's follower count.

Get the comment thread on one Facebook post, including nested replies. The response carries total_count (top-level comments on this post, independent of the `before` cursor) — use that for a count instead of paginating to the end. Rate-limited per business alongside the other Facebook list tools; a 429 means back off rather than retrying in a loop.

Get one order in full: line items with variations, customer and delivery address, delivery option and cost, discounts, totals, status timestamps, and courier/consignment details when dispatched. Owner-only.

Check whether products have been extracted from a Facebook post: pending, processing, completed, no_products or error. Read this before calling extract_products_from_post so you don't re-run work that already finished.

Get one product in full: description, pricing, bargain percent, per-variation stock and images, and any active discounts. The response also lists any campaigns this product is attached to, each with its OWN `images` array — those belong to the campaign, not to this product. Only `product.images` is this product's own photo list; never copy a URL from a campaign's `images` into update_product's `images` field for this product, it will be ignored (campaigns and products store images separately).

Check the Shopify connection and which shop is linked. Connecting requires Shopify's own browser OAuth flow, done in the app.

Read Steadfast delivery analytics for one of several views: overview, monthly-revenue, demographics, delivery-performance, payment, comparative, trends or forecast. delivery-performance is the one that shows the successful-vs-returned split, which is the number that decides whether cash-on-delivery is working for this merchant.

Check whether Steadfast courier is connected, and read the account balance. Check this before suggesting any courier workflow. To connect Steadfast, use create_steadfast_setup_link — no tool here ever takes the API key/secret directly, and none can read a stored credential back.

Get the business's store code — the code an employee types during signup to join this workspace. Owner-only; an employee account gets a 403. Treat it as sensitive: anyone with it can request to join the workspace, so give it to the merchant, don't scatter it into a shared transcript.

Get storefront funnel analytics: total tracked events, storefront views, product views, add-to-cart, purchases, conversion rate, add-to-cart rate, open orders and fulfilment rate, plus top products, referrers, locations, networks, devices, platforms, top categories, top customers, cart additions and low-stock products. Owner-only — an employee account gets a 403. Read the numbers honestly: most Seller AutoBusiness stores are small, so a conversion rate off a few dozen sessions is noise, not a trend. Say when there is too little data rather than narrating a story into it.

Check whether the connected account's email and phone number are verified. Unverified email is a common reason other actions behave unexpectedly, so check here before concluding something is broken.

Import orders from Daraz into this app's order system.

Import products from Daraz into this catalog, matching on Daraz product id so a re-run updates rather than duplicates. Counts against the plan's product limit — check get_account_usage first.