MerchantDrafts · Docs

Get Premium Feature Guide

Feature-row guide for Get Premium, including Opportunity Radar and Opportunity Strategist gating by plan.

Get Premium Feature Guide

Use this guide while comparing packages on the Get Premium page.

It explains what each feature row means in practical WooCommerce terms, without overloading the pricing table itself with long descriptions.

Think of this page as a buying guide, not just a glossary. Each row answers a slightly different decision question:

When two plans look similar on surface features, the real difference is usually in site count, hosted headroom, continuation path, and how much operational control the package gives you.

Current truth boundary:

Current direct operator ladder used on Get Premium:

Opportunity Radar Workspace

The Opportunity Radar workspace is the operator decision table for prioritizing what to act on next across stock, demand signals, and business lanes.

Current Get Premium gating:

Opportunity Strategist

Opportunity Strategist is one capability and one row in the comparison model. It is not split into separate scope/selected-product rows.

Current Get Premium gating:

Practical note for buyers:

Monthly price

The recurring subscription price for the direct hosted Get Premium ladder.

This is the right row for comparing the ongoing cost of each package when the buyer is choosing between direct monthly plans.

On the direct ladder, monthly price should always be read together with Included hosted credits, Sites included, and Overflow / refill policy. A low monthly price can still be the wrong plan if the store will routinely burn through the hosted pool and need constant refill or upgrading.

Sites included

How many WooCommerce sites may run under the same license package.

Site count is a packaging control, not a multiplier for hosted credits. If a package includes 3 sites and 300 hosted credits, the hosted credits still belong to the license unless the package docs say otherwise.

This matters most for agencies and multi-brand operators. A package with more sites included is not just a volume upgrade. It changes how widely the same commercial plan can be deployed across client stores or internal projects.

Included hosted credits

The hosted MerchantDrafts credit pool included with the direct monthly package.

On Get Premium, this is the recurring monthly hosted allowance that resets each billing cycle.

This row tells you how much MerchantDrafts-hosted generation is built into the subscription before refill, upgrade, or BYOK decisions come into play. It is the clearest signal of how much routine hosted work the plan is designed to carry.

Overflow / refill policy

What happens when the included monthly hosted credits are used up.

Typical continuation paths are:

This row matters because two plans may both include the same core feature set while feeling very different operationally after the included pool is used. On the lower paid plans, refill is mostly a convenience overflow path. On agency-capable plans, refill sits alongside BYOK as a choice between simplicity and direct provider control.

Long-term usage model

The intended ongoing operating model for the package after the initial setup period.

Examples on the direct ladder include:

This row is the best answer to the question, What is this plan really meant to become once it is part of our normal workflow? Some plans are designed to stay comfortably hosted. Others are designed to start hosted and give the operator a cleaner path into direct Gemini usage later.

Content generation

WooCommerce product-content generation for the core product editor flow.

In MerchantDrafts, this row does not mean one paragraph of AI copy. It means the full Content Tab package used in the single-product editor and reused in the Products Workspace review/writeback flow.

The content-generation package includes:

That means one generation run prepares both the visible product-page copy and the supporting product metadata around it. In practical WooCommerce terms, the operator is not only drafting the body copy. They are also preparing the product's short sell-through summary, search snippet, image metadata, and catalogue tags in one pass.

The field logic is structured, not free-form:

Current description-length targeting is:

The long description also follows the output-format setting:

The generated package is then used across the UI like this:

For SEO persistence, the meta description is not only shown in the MerchantDrafts panel. On write/apply, MerchantDrafts also saves it to its own meta and writes to supported SEO-plugin keys such as Yoast, Rank Math, and AIOSEO variants where available.

A realistic generated package can therefore look like:

`

This is why Content generation is the row that usually determines whether MerchantDrafts is a real operational product for the store. If this row is enabled, the package can cover the core WooCommerce writing workflow, not just a supporting AI utility.

Marketing Material

The campaign and channel-copy workspace for marketing outputs beyond the main product page.

In MerchantDrafts, this means the Marketing Material area is available, not just one loose ad-copy box. It is a workspace family with separate platform tabs and platform-shaped outputs.

The current workspace set includes:

These tabs do not all generate the same kind of output. Each one has its own structure:

Operationally, this workspace is for review and copy, not for writing over WooCommerce product fields. Product content belongs to the Content Tab and product writeback flow. Marketing Material belongs to channel-specific publishing work that sits downstream from the product page.

This row therefore means the plan supports:

This row signals whether MerchantDrafts can help beyond the product page itself. Stores that publish across multiple channels usually feel the value of this row quickly because it reduces the need to rewrite the same selling message for each platform from scratch while still respecting each platform's format constraints.

Lifestyle image generation

The hosted visual workflow for creating lifestyle-style product scenes and related image outputs.

This sits apart from normal text generation because it has different cost behavior, a separate review flow, and a more structured visual workflow than the text fields in the Content Tab.

In MerchantDrafts, the Lifestyle Images feature is not just generate a picture. It is a step-based flow that starts from the product's real featured image and then builds outward:

The text-generation package prepares part of this workflow in advance by producing 3 Background Scene Prompts for later use in Step 3. Those prompts are written in English and are intended as ready-to-use starting points for realistic lifestyle background generation.

So when a plan includes Lifestyle image generation, it effectively includes:

This matters because many stores do not just need product copy. They need visual merchandising support too. In practice, the combination often looks like:

That makes this row commercially meaningful in a different way than text-only rows. It is not only about output volume. It changes the kind of merchandising work the package can support.

Products bulk editing workspace

The WooCommerce products workspace for bulk generation, review, and write-back.

This is the catalogue-level operational surface inside MerchantDrafts → Products Workspace. It is separate from the single-product editor and separate from WooCommerce's native bulk edit.

The real workflow is:

The generated package here is the same structured package used in the single-product flow:

The workspace also exposes operational states that matter for teams:

And it includes review tooling such as:

There are also safeguards for large runs:

For catalogue-heavy stores, this workspace often matters more than the single-product editor because it turns MerchantDrafts into an operational tool rather than a one-off drafting assistant.

Categories bulk editing workspace

The WooCommerce categories workspace for generating and writing category-level descriptions and context.

This workspace manages category descriptions at the WooCommerce category level and also helps shape Category Context, which can become part of the prompt layer for product generation.

That makes it more than a simple category-description writer. It supports the catalogue structure behind the product pages:

This is useful when the operator wants MerchantDrafts to improve the catalogue structure, not only the individual product layer.

In practice, this helps stores keep category pages aligned with the same brand voice and merchandising logic used across the rest of the catalogue, while also giving product generation better category-aware guidance.

Manufacturers bulk editing workspace

The WooCommerce manufacturers or product_brand workspace for generating and maintaining manufacturer descriptions in bulk.

This workspace manages native WooCommerce manufacturer or brand descriptions in bulk. In MerchantDrafts, manufacturer descriptions are not just editorial filler. They can also serve as an optional prompt layer for core product generation when that setting is enabled.

So this workspace helps in two ways:

This helps stores that rely on manufacturer or brand pages as part of the shopping experience.

This feature becomes more important on stores where brand landing pages carry SEO value, trust signals, or navigation importance for shoppers.

MerchantDrafts AI engine

The shared MerchantDrafts generation engine and prompt-layer system behind the package.

This row signals that the package uses the full MerchantDrafts runtime rather than a stripped-down shell.

In practice, that means generation is assembled through a layered system, not a one-line prompt. For core product content, MerchantDrafts combines layers such as:

It also tells the operator that the same structured generation logic, prompt assembly, and catalogue-aware behavior are present across the included workspaces, not just a single narrow content surface.

Specialist AI agents

The structured expert-style assistant flows built for channel and marketing tasks.

These are not generic chatbots. They are workspace-aligned conversational panels designed around specific publishing contexts and copy workflows.

The current agent family follows the channel structure of Marketing Material, with specialist agents for:

These agents are used to:

This matters because specialist flows reduce prompt-writing effort for the operator. Instead of starting from an empty box, the workflow already understands the intended format, channel expectations, and task shape.

Power Tools

The advanced operator control surface for prompt editing, prompt inspection, and runtime-oriented controls.

Power Tools is the advanced operator surface inside Settings for inspecting and shaping how MerchantDrafts behaves.

At this stage, it is the home of controls such as:

This means the operator can:

Power Tools is aimed at more advanced WooCommerce operators who want to tune how MerchantDrafts behaves without dropping into engineering-only tooling.

This feature is especially valuable for teams that want tighter control over prompts, inspect what the runtime is doing, or adapt generation behavior for more complex catalogue situations.

BYOK

BYOK means Bring Your Own Gemini Key.

When BYOK is enabled on a direct package, the operator can switch the runtime mode in About / License from Hosted to BYOK and save their own Gemini API key.

The practical runtime difference is:

That means BYOK changes:

Operationally, BYOK is less about more features and more about more control. It changes who pays the provider bill, who owns the provider relationship, and which runtime path the store depends on day to day.

White label

White label allows the operator to replace visible MerchantDrafts branding on client-facing or agency-managed sites.

Typical white-label controls include:

At the current product scope, white label is primarily a UI-level rebrand, not a deep architectural fork. That means the visible plugin layer can be rebranded for client-facing use while the internal identifiers and system internals still remain MerchantDrafts under the hood.

This row is usually most relevant for agencies, resellers, or internal teams deploying MerchantDrafts into a client-facing environment where MerchantDrafts branding should not be the visible product layer.

AI Support Assistant

The operator-facing support assistant included in the product support experience.

This is the in-product help assistant used in the Support Hub to answer questions about MerchantDrafts usage, workflows, setup, and troubleshooting.

It is separate from:

Its job is support and onboarding, not output production. In other words, it helps the operator understand how to use the product, what a workspace does, why something failed, or what the next step should be.

It should be read as a support and onboarding feature, not as part of the catalogue generation quota. Its job is to help operators use the system more effectively, troubleshoot workflows, and understand what the product is doing.

MerchantDrafts Docs · support@merchantdrafts.com · Main site