Blueprints and foundations

The short version: how, what, and this one

Specific choices win. A Foundation might default to one shipping policy; a furniture Blueprint can use a different policy; and the draft for one local-pickup chair can override both. Reuse should save typing, not take away judgment.

Your Foundation is the business-wide base

letsList creates a default Foundation for your eBay account. You normally review it once, then return only when your business rules change. It supplies the values that should not need to be re-entered for every new listing.

• Ship-from country, city, postal code, and currency
• Payment, return, and shipping policies
• Handling time, listing format, and listing duration
• Business-wide AI guidance, such as tone or standard seller promises

Keep this layer broad. A return policy belongs here. A default category for vintage cameras does not, because the Foundation also applies when you list a book or a jacket.

A Blueprint captures item-class judgment

Blueprints are optional and seller-created. Make one when you repeatedly list the same kind of thing and find yourself making the same choices or giving AI the same instructions. A useful Blueprint is closer to “Used books” than to “Tuesday's blue hardcover.”

• A category that usually fits this class of item
• Condition-description language that should start every item in the class
• A shipping policy or package pattern that is specific to the class
• AI guidance about the facts buyers expect for that type of item

Good AI guidance names what to inspect, not what to invent. A book Blueprint might say “look for edition, ISBN, binding, highlighting, and ex-library marks.” The photos and seller notes still determine which of those facts are actually true.

Applying a Blueprint stamps the draft

You can choose a Blueprint while creating drafts from SKUs or apply one inside the listing editor. At that moment, its settings are copied into the draft as an override layer and its AI guidance becomes context for the item.

This boundary keeps reusable defaults predictable. A template can accelerate a draft, but the draft remains an editable record of what you intend to publish for one SKU.

A practical setup sequence

1. Open Foundations and verify your location, currency, policies, handling time, and business-wide AI guidance.
2. Create a Blueprint only for an item class you expect to list repeatedly.
3. Give the Blueprint a short code and a clear name that your team will recognize.
4. Add class-specific category, condition, shipping, and AI guidance defaults.
5. Select the Blueprint when creating a draft, then inspect and edit the actual item.
6. Review the finished draft before publishing. The individual item always gets the final decision.

Common mistakes

• Putting item-class rules in the Foundation. If the rule is only true for books, clothing, or electronics, put it in a Blueprint.
• Making a Blueprint for every item. One-off facts belong on the SKU or draft. Blueprints earn their keep through repetition.
• Treating AI guidance as item data. Guidance tells AI what to inspect and how to write. It does not prove a brand, model, condition, or identifier.
• Expecting template edits to rewrite live inventory. Foundations and Blueprints initialize work; publishing remains an explicit per-listing action.