Before connecting 7BE, check repeat-purchase fees and what remains after you leave

7BE’s store traffic service charges for orders attributed to AI, but repeat purchases by AI-acquired buyers within 12 months may also incur fees. Before adopting it, check what happens to product content and product feeds after deactivation, as well as the data flows introduced by review invitations.

Source: 7be.io
November 9, 2026
5 min

“Pay only when AI brings sales” can lead merchants to see 7BE as a customer-acquisition service that charges only for the first purchase. In an actual assessment, two further questions matter: whether repeat purchases by the same buyer count, and whether generated product content remains after you stop using the service.

This article covers the 7BE store traffic service checked for this review, without mixing in material about its historical agency-matching business. Based on the current official website, WooCommerce plugin documentation, and privacy policy, a more cautious basis for adoption is that you accept ongoing order reconciliation using the platform’s recorded attribution criteria and are willing to arrange alternatives for content and feeds after deactivation. This article does not test incremental traffic or attribution accuracy.

A chargeable order does not necessarily involve a new AI visit

The 7BE homepage states that the service fee is 10% of net sales from AI orders. Net sales deduct discounts and refunds and exclude taxes and shipping. An easier detail to overlook is that buyers brought in by AI are counted for 12 months, with subsequent orders during that period included regardless of which channel they use to return.

Suppose a new customer’s first order has a net value of USD 100. Four months later, they return directly through a bookmark and buy another USD 80 net of products. Under the description on the page, provided the service remains active, both orders are chargeable, and there are no refunds or other adjustments, the total service fee is USD 18, rather than USD 10 charged only on the first order. This example applies the rules; it is not an actual bill, nor does it mean 7BE can prove that it alone caused the second order.

Repeat-purchase businesses should therefore assess costs against the customer’s contribution margin over the observation period, rather than comparing only first-order acquisition fees. An “AI order” label in the dashboard tells you how the platform classifies an order. The merchant’s question, “Would this sale have happened without the service?”, requires a separate before-and-after observation or comparison design. Attribution labels alone cannot answer it.

The homepage also says merchants can mark orders as non-AI to remove charges, with fees already billed credited against future invoices. During a trial, identify questionable orders, compare them with your own records, and make sure someone on the team is responsible for a monthly review rather than simply looking at the dashboard’s total sales figures.

When you deactivate, displayed content leaves too

The official WooCommerce plugin page defines newly generated summaries, Q&As, and similar content as part of an ongoing service: they appear in product-page blocks rather than being written into the product’s main content. Those blocks disappear when the plugin is disconnected, deactivated, or deleted, or when the service ends. The documentation also says that 7BE being unreachable for 24 consecutive hours triggers removal of the displayed content.

This changes how a trial should be evaluated. A product page becoming more complete after adding Q&As does not mean the merchant has acquired a permanent page-improvement asset. Core product specifications, compatibility conditions, and delivery promises should still appear accurately in content maintained by the merchant. Explanations cannot depend solely on external blocks.

The official website also states that product feeds stop updating after deactivation and their links expire after 14 days; verified reviews remain on the store’s page on 7be.io. When planning an exit, check in-store displays, external product feeds, and off-site reviews separately. “Stopping charges” does not mean all three are cleared at the same time. If current operations depend on any of them, prepare alternative content or a way to supply it before disconnecting the service.

Enabling reviews expands the scope of data

The privacy policy, updated on November 5, 2026, distinguishes attribution billing from verified reviews. The former processes fields such as order amounts, dates, and sources, and uses a one-way identifier to recognize repeat purchases. Once review invitations are enabled, it receives buyers’ names, email addresses, and product information to send one invitation and one reminder.

Thus, “attribution does not receive buyer names or email addresses” cannot be generalized to mean that the entire service never receives that information under any settings. Operations teams should treat reviews as a separate activation decision, confirm their notice, permissions, and customer communication arrangements, and only then let real orders enter the workflow. Connecting the plugin is not a reason to assume that every additional data use suits the existing business.

7BE also explicitly does not guarantee that a store will appear in AI recommendations. For a new channel worth trying, a reasonable first-stage goal is to establish whether attributed orders, repeat-purchase fees, and funds actually received reconcile, observe how product content is displayed, and confirm which content disappears on exit. Expand use only when all three boundaries are acceptable. If the team needs to retain generated content permanently, or is willing to pay only for provably incremental first orders, clarify those conditions with the provider first.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:7be.io