MerchantDrafts · Docs

Partner Deals Feature Guide

What each comparison row means on the Partner Deals packaging page.

Partner Deals Feature Guide

Use this guide while comparing packages on the Partner Deals page.

It explains what each partner-deal comparison row means so operators can compare LTD and marketplace packaging without relying only on shorthand table labels.

On the partner ladder, the important question is usually not just What do I get on day one? but How does this package behave after activation? That is why the partner table needs rows such as starter credits, refill policy, and long-term usage model, not only raw feature checkmarks.

Current truth boundary:

One-time price

The one-time purchase cost for a partner or LTD package.

This row is used for marketplace-style offers where the buyer pays once for the package itself and then continues through the included starter credits, PAYG refill, or BYOK path defined by that package.

This row should never be read in isolation. A lower one-time price may still lead to a weaker operational fit if the site count, starter-bank size, or continuation model does not match how the buyer expects to use the product after activation.

Sites included

How many WooCommerce sites may use the same partner package.

Site count is one of the strongest packaging levers for LTD deals and partner offers. It is not a multiplier for hosted credits unless the commercial docs explicitly say so.

For partner offers, site count often separates casual solo buyers from agency or reseller buyers. It is one of the cleanest ways to differentiate tiers without changing the core product story.

Included hosted credits

The hosted MerchantDrafts credits included with the partner package at activation time.

On Partner Deals, this is the hosted starter bank that gives the buyer useful runway immediately after activation.

That starter bank is important because many partner buyers want the product to work immediately without first setting up BYOK or making an additional refill purchase. It is activation runway, not a claim of infinite hosted usage.

Overflow / refill policy

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

Typical continuation paths are:

This row tells the buyer how forgiving the package is after the starter credits are gone. A good partner package should not strand the operator after activation. It should make the next step obvious, whether that is refill, BYOK, or a mixed operating model.

Long-term usage model

The intended operating pattern after the initial starter bank is used.

Examples on the partner ladder include:

This is the best row for answering, After the LTD promise is over, how is the package supposed to live in the real world? It helps prevent misleading assumptions about lifetime hosted usage.

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:

`

On the partner ladder, this row matters because it reassures buyers that the LTD or marketplace package is not just a promotional shell with a few supporting tools attached. If this row is enabled, the package is still a real MerchantDrafts content-production package capable of handling the core WooCommerce writing workflow after activation.

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 package supports:

For partner buyers, this row signals whether the package is useful only for catalogue maintenance or also for broader marketing work once the product is adopted.

Lifestyle image generation

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

This matters especially on partner packaging because image-heavy usage can change the economics and refill behavior faster than plain text generation.

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 partner package includes Lifestyle image generation, it effectively includes:

In practical use, the package often looks like:

That is why this row is worth calling out directly instead of hiding it under a generic generation label. It affects perceived value, activation quality, and long-term refill behavior.

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 agencies and marketplace buyers, this row often signals whether the product can support real operational throughput rather than one-off manual drafting.

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 helps improve category landing pages and catalogue structure, not just product-by-product content.

It is especially useful for stores that care about category merchandising, SEO, or maintaining a coherent information architecture across the shop.

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 is useful for stores where manufacturer or brand pages matter commercially.

On larger catalogues, this can save a lot of repetitive editorial work that would otherwise sit outside the main product workflow.

MerchantDrafts AI engine

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

This row signals that the partner package is using the same MerchantDrafts runtime, not a simplified demo 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 helps reassure buyers that the partner packaging is commercial packaging, not a separate lower-grade product branch.

Specialist AI agents

The structured expert-style assistant flows built for marketing and publishing 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:

That makes them especially useful for teams that want guided output generation without relying on staff to become strong prompt writers first.

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:

This is where more advanced operators and agency-style users can inspect and tune how MerchantDrafts behaves.

On partner tiers, Power Tools often marks the point where the package becomes suitable for more hands-on operators who want to understand and shape the generation layer more directly.

BYOK

BYOK means Bring Your Own Gemini Key.

When BYOK is enabled on a partner 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:

This gives the buyer a control-oriented path after activation. It is particularly valuable for agency buyers who want the flexibility to keep the easy hosted start while still having a direct-provider option later.

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 matters mostly for resellers, agencies, and client-service teams that want MerchantDrafts capabilities without exposing MerchantDrafts as the visible product brand.

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.

In a partner context, this row is useful because it supports onboarding and lowers friction after activation, especially for less technical buyers who need the product to feel guided rather than self-service-only.

MerchantDrafts Docs · support@merchantdrafts.com · Main site