GPTWala

Tag: wholesale sales

  • Line Sheet vs Catalogue vs Lookbook: Choose the Right Sales Document

    A line sheet, catalogue and lookbook can contain the same products, but they solve different buyer problems. A line sheet supports selection and ordering, a catalogue explains a broader range, and a lookbook creates context and desire. Confusing them produces beautiful files that cannot take an order or dense files that do not tell a persuasive story.

    This comparison sits beneath GPTWala’s digital product catalogue strategy and helps manufacturers, wholesalers and product brands choose a practical document set.

    Contents

    1. Use the buyer job as the main distinction
    2. Build a line sheet for a specific selling window
    3. Use a catalogue for range understanding and comparison
    4. Use a lookbook to create context and confidence
    5. Choose with a simple decision matrix
    6. Create one product-data backbone
    7. Design for the chosen format and device
    8. Connect each document to a sales handoff
    9. Control versions and measure usefulness
    10. Frequently asked questions
    11. Sources and further reading

    Use the buyer job as the main distinction

    The document name matters less than the task it supports. A wholesale buyer needs identities, variants, prices, minimums, packs, delivery information and an order route. A technical evaluator may need specifications and documents. A press, retail or brand audience may need collection story, styling and strong imagery.

    Document Primary buyer job Typical density
    Line sheet Select and order a defined range High commercial density
    Catalogue Discover and compare products or families Moderate to high information density
    Lookbook Understand mood, use and collection story Low data, high visual emphasis
    Order form or portal Submit quantities and terms Transactional structure

    JOOR describes line sheets as shopability-focused, while lookbooks emphasise visual presentation. Shopify’s wholesale guide similarly treats a ready line sheet and order form as operating basics.

    Build a line sheet for a specific selling window

    A line sheet should let a buyer scan products and prepare an order with minimal back-and-forth. Include brand and contact, season or validity, product name, style or SKU, clear image, variants, size or pack, wholesale price, suggested retail price when relevant, MOQ or case pack, order deadline, delivery window and terms reference.

    Line-sheet field Buyer decision Control
    SKU and product name Identify order line Match product master
    Image Confirm item and variant Use current approved view
    Variants Choose valid combination Use controlled labels
    Wholesale price Assess commercial fit Currency, unit and validity
    MOQ or case pack Build viable order State per item or range
    Delivery window Plan receipt Use approved basis

    Keep account-specific discounts or confidential terms inside the permitted sales process. Link the line sheet to the approved pricing strategy.

    Use a catalogue for range understanding and comparison

    A catalogue can cover families, applications, selection logic, shared specifications, product summaries, authentic images, documents and enquiry actions. It may be public or audience-restricted. Compared with a line sheet, it can explain more and order less.

    A technical B2B catalogue should not be reduced to lifestyle photography. It must help buyers rule products in or out. A consumer catalogue may emphasise benefits and presentation while still keeping prices, variants and availability accurate.

    Catalogue layer Content Buyer outcome
    Overview Range, audience and navigation Find relevant family
    Family Selection logic and comparison Narrow options
    Product Identity, attributes and proof Confirm candidate
    Reference Terms, symbols, documents and contact Understand conditions
    CTA Enquiry, sample, quote or web purchase Move to action

    Use the product copy template for controlled explanations and the product SEO guide for web counterparts.

    Use a lookbook to create context and confidence

    A lookbook shows how a range feels, combines or performs in context. It uses editorial sequences, application scenes, detail views and concise captions. It can support launches, sales appointments, retail buying, press or social storytelling.

    Prices are optional because the job may be persuasion rather than ordering. If commercial information is included, make it current and clearly scoped. Do not rely on the lookbook as the only product record; every featured item should map to a stable identity in the line sheet, catalogue or website.

    Lookbook element Purpose Control
    Collection story Frame the range Use approved positioning
    Hero imagery Create attention and context Preserve product truth and rights
    Product caption Connect image to item Include stable name or code
    Styling or application Show combination or use Avoid misleading scale or performance
    Next step Move to selection Link current line sheet or catalogue

    Apply the catalogue photography workflow so visual ambition does not create inaccurate products.

    Choose with a simple decision matrix

    Start with the next buyer action

    Ask who receives the document and what they must do immediately after reading. A distributor choosing a full assortment may need a catalogue plus line sheet. A retailer at a buying appointment may start with a lookbook and finish in a line sheet or portal. A technical buyer may need a catalogue plus controlled data sheets and quotation.

    Situation Lead document Supporting document
    New wholesale range review Lookbook or curated catalogue Line sheet and order form
    Repeat wholesale order Line sheet or portal Current terms and stock view
    Technical product discovery Catalogue Data sheet and enquiry
    Retail launch story Lookbook Product pages and buying link
    Trade meeting Short catalogue Account-ready line sheet

    Do not build three independent sources. Build three views from the same approved product data and asset library.

    Create one product-data backbone

    Maintain product identity, variants, attributes, images, rights, pricing, MOQ, pack, availability and lifecycle in controlled systems. Each sales document consumes the fields it needs. GS1’s product-data standards demonstrate the value of harmonised attributes across channels.

    Master field Line sheet Catalogue Lookbook
    SKU and identity Required Usually present Caption or mapped reference
    Wholesale price Usually required Optional by audience Usually omitted
    Technical attributes Selection minimum Detailed where relevant Rarely detailed
    Imagery Clear product view Product and supporting views Editorial emphasis
    MOQ and delivery Required for order May be summarised Usually omitted

    Use GPTWala’s fact-safe AI description method if AI assists with variants, but approve language against the product master.

    Design for the chosen format and device

    A line sheet needs aligned grids, repeated field positions and enough space to mark quantities. A catalogue needs hierarchy, contents, comparisons and readable evidence. A lookbook needs rhythm, image quality and captions that do not compete with the story. All need legible text, contrast, descriptive links and a usable reading order.

    For digital use, test narrow screens, ordinary laptops, downloads, links and search. A wide line-sheet table may work better as a portal than a phone PDF. W3C accessibility guidance should inform web versions and downloadable documents.

    Format Strength Limitation
    Responsive web Searchable, linkable and updateable Requires maintained website
    Buyer portal Current availability and ordering Access and onboarding needed
    Screen PDF Portable and familiar Can become stale and hard on phones
    Print Useful in meetings and field sales Cannot update after distribution

    Connect each document to a sales handoff

    Put a current contact, buyer action and product context where the reader needs them. A line sheet should point to the order or quotation route. A catalogue should carry the selected family or SKU into an enquiry. A lookbook should link a featured item to selection detail.

    For message-led selling, use the WhatsApp catalogue workflow as a lightweight transactional layer, not as a replacement for a complete B2B record. Send leads into the B2B lead-generation and follow-up system.

    Document action Context to carry Owner
    Order enquiry SKUs, quantities and buyer Sales operations
    Technical question Product and application Technical sales
    Sample request Variant, quantity and location Assigned sales owner
    Range presentation follow-up Buyer, selected items and timing Account owner

    Control versions and measure usefulness

    Show title, audience, currency or market where relevant, release status and owner. Retire old downloads, buyer links and printed stock. A date alone does not explain what changed; keep a change summary and product-level source.

    Measure buyer use according to job: line-sheet orders and clarification rate, catalogue searches and qualified enquiries, lookbook product clicks and appointments. Sales feedback should identify missing fields and confusing comparisons, not merely praise visual quality.

    Document Quality metric Maintenance trigger
    Line sheet Order completeness and correction rate Price, range, MOQ or delivery change
    Catalogue Qualified selection and enquiry Product, proof or navigation change
    Lookbook Movement to product or appointment Collection, rights or campaign change
    All Broken links and stale versions Any master-data or contact change

    Keep all three aligned to the brand identity system while preserving their distinct jobs.

    Frequently asked questions

    What is the difference between a line sheet and a catalogue?

    A line sheet is a compact wholesale selection and ordering document. A catalogue explains a broader range, comparison logic and product evidence.

    What is the difference between a line sheet and a lookbook?

    A line sheet prioritises identities, variants, prices, minimums and ordering. A lookbook prioritises collection story, context and imagery.

    What should a wholesale line sheet include?

    Include contact, validity, product names, SKUs, images, variants, wholesale price, relevant retail price, MOQ or pack, delivery window, terms reference and order route.

    Does a lookbook include prices?

    It can, but prices are often omitted when the purpose is storytelling. Any price shown must state its audience, currency, unit and current validity.

    Do manufacturers need both a catalogue and a line sheet?

    Many do when buyers first need range and technical understanding, then a concise commercial document for selection or ordering.

    How often should sales documents be updated?

    Update them after relevant product, price, pack, availability, rights, contact or policy changes and review active documents on a fixed cadence.

    Sources and further reading

  • Quotation Follow-Up System for Manufacturers and Wholesalers

    A quotation follow-up system should help the buyer make a decision and help the seller learn what is blocking it. It is not a schedule of repeated “just checking” messages. The system begins before the quote is sent, with clean requirements, clear scope, an agreed review step and one owner. It ends with an explicit outcome or a documented future trigger.

    Place this workflow inside GPTWala’s CRM structure for manufacturers and wholesalers so every open quote has a status, next action and accountable person.

    Contents

    1. Set the follow-up before creating the quotation
    2. Make the quotation easy to evaluate
    3. Create explicit quote stages and reason codes
    4. Use a context-led follow-up cadence
    5. Write follow-up messages that add information
    6. Route objections instead of arguing by message
    7. Automate reminders and records, not judgement
    8. Control versions, approvals and personal data
    9. Measure the quote funnel without misleading averages
    10. Use stage-based templates with human context
    11. Run a weekly open-quote review
    12. Frequently asked questions
    13. Sources and further reading

    Set the follow-up before creating the quotation

    Confirm the requirement, decision roles, quantity, delivery location, technical questions, commercial constraints and target decision date. Ask how the buyer will evaluate the quote and agree when to review it. A quotation sent without this context often becomes an unowned attachment.

    Pre-quote field Reason Minimum evidence
    Requirement Prevents quoting the wrong solution Buyer-confirmed specification or brief
    Decision process Shows who and what affects approval Roles, checks and target timing
    Commercial scope Prevents hidden cost disputes Quantity, taxes, freight and terms basis
    Review step Creates a legitimate next contact Date, channel and participants

    Make the quotation easy to evaluate

    Use a controlled quote number, version, issue date, validity, buyer identity, item description, quantity, unit, price basis, taxes, freight, delivery basis, payment terms, exclusions and acceptance route. State variables and assumptions clearly. If an engineering or installation scope is separate, do not hide it inside a vague line item.

    Link the relevant product data sheet or maintained digital catalogue instead of attaching uncontrolled files. Ensure that the quote and sales record refer to the same product and version.

    Create explicit quote stages and reason codes

    Use stages that reflect buyer reality, not seller optimism. Suggested stages are draft, internally approved, sent, receipt confirmed, under review, clarification or revision, commercial decision, accepted, declined, expired and nurture. Every active stage needs a next action and date.

    Stage Required next action Exit evidence
    Sent Confirm access and review date Buyer received or opened through an approved system
    Under review Answer a specific question or wait for agreed date Buyer status or meeting outcome
    Revision Record requested change and approval New controlled version issued
    Accepted Confirm order, payment and fulfilment handoff Purchase order or agreed acceptance
    Declined Capture reason and alternative Buyer response or documented closure
    Nurture Record the real future trigger Date, event or condition

    Use a context-led follow-up cadence

    There is no universal best day for every quotation. A standard stocked item, custom manufacturing project and distributor agreement have different review cycles. Use the date agreed with the buyer, quote validity, production capacity and internal buying process. When no date was agreed, a short receipt confirmation followed by a reasonable review interval is safer than daily pressure.

    Contact Purpose Useful question
    Receipt check Confirm the quote is accessible and complete Did the file arrive and is any information missing?
    Review follow-up Remove a decision blocker Which technical or commercial point needs clarification?
    Value follow-up Add relevant evidence Would a data sheet, sample or application call help?
    Decision check Confirm status and next step Is the requirement active, changed or paused?
    Close-loop message Stop indefinite chasing Should we close this version and revisit at a named trigger?

    Write follow-up messages that add information

    Reference the requirement and quote number, summarise the purpose, add one relevant fact or answer, and ask one clear question. Keep the message short enough to reply to. Avoid invented scarcity, false deadlines, exaggerated results and generic attachments. Shopify’s sales follow-up guidance similarly frames proposal follow-up around the specific offer, buyer concern and a useful next step rather than a context-free reminder.

    Use the buyer’s channel preference. If WhatsApp is used, follow the current WhatsApp Business Messaging Policy and keep evidence of opt-in for business-initiated messages. Review GPTWala’s WhatsApp consent workflow.

    Route objections instead of arguing by message

    Classify the blocker: technical fit, price or terms, timing, internal approval, competitor comparison, missing document, trust, no budget or no response. Send the right owner and evidence. A technical objection may need an application specialist; a price objection may reveal a quantity or scope mismatch; a timing objection may need a future trigger.

    Blocker Diagnostic question Possible response
    Technical fit Which requirement is not yet proven? Data, sample, drawing or specialist call
    Price Which option or assumption is being compared? Clarify scope, quantity and total cost
    Timing What event controls the purchase? Record project or budget trigger
    Approval Who needs what evidence? Provide an approval-ready summary
    No response Is the requirement still active? Close the loop respectfully after the defined sequence

    Automate reminders and records, not judgement

    Automation can create tasks, send receipt acknowledgements, surface quotes without a next action and stop a sequence when the buyer replies. It should not send repeated messages after a decline, ignore a changed scope or invent personalisation. Keep templates by stage and require the owner to review high-value or sensitive communications.

    Connect automation to the small-business marketing automation framework, but separate marketing nurture from an active commercial quotation. A buyer can opt out of promotional communication while still receiving necessary transactional information through an appropriate channel.

    Control versions, approvals and personal data

    Only authorised people should issue or revise prices and terms. Preserve quote versions, approval evidence and the reason for a change. Restrict customer contact, drawings, pricing and payment information to people who need it. Do not paste confidential buyer data into unapproved tools.

    Provide clear notices and respect applicable rights and withdrawal where personal data processing relies on consent. The DPDP framework has phased commencement and should be applied with qualified legal advice to the business’s facts.

    Measure the quote funnel without misleading averages

    Track quote count and value, time to issue, time in stage, revision rate, response rate, acceptance rate, lost reasons, discount pattern and revenue. Segment by product, source, buyer type, owner and complexity. A large engineered quote should not be compared with a repeat wholesale order as if their cycles were identical.

    Metric Definition control Decision use
    Time to quote Complete requirement to sent quote Find estimating bottlenecks
    Review engagement Buyer response or meeting after send Diagnose handoff quality
    Revision rate Quotes with controlled revisions Find scope or pricing ambiguity
    Acceptance rate Accepted quotes divided by eligible closed quotes Compare like-for-like segments
    Loss reason coverage Closed-lost quotes with valid reason Improve product, offer and process

    Use stage-based templates with human context

    Create a small approved library: receipt check, clarification, review invitation, revised quote, final validity reminder and close-loop message. Each template should contain editable context fields and one clear question. Train the team to remove irrelevant lines rather than sending the template unchanged.

    Use GPTWala’s lead-qualification guide before quoting so sales does not use the follow-up stage to discover basic fit that should have been established earlier.

    Run a weekly open-quote review

    Review every open quote for current version, buyer status, next action, next date, owner, blocker and commercial risk. Close expired or dead records with evidence instead of leaving them permanently open. Escalate capacity or delivery promises that no longer match operations. Monthly, analyse loss reasons and revise qualification, quote design or proof assets based on repeated patterns.

    Frequently asked questions

    How do you follow up after sending a quotation?

    Confirm receipt, follow the agreed review date, address one specific blocker or add relevant evidence, and ask one clear question tied to the buyer’s decision.

    When should you follow up on a quote?

    Use the review date agreed with the buyer and the real buying cycle. If none was set, confirm receipt and choose a reasonable interval based on complexity and urgency.

    What should a quotation follow-up message say?

    Reference the requirement and quote number, state why you are contacting the buyer, add useful context and end with one easy-to-answer question.

    How many times should you follow up on a quotation?

    There is no universal number. Use a defined sequence appropriate to the deal, stop when the buyer declines or opts out, and record a real future trigger when timing changes.

    Can quotation follow-up be automated?

    Tasks, acknowledgements, reminders and sequence stopping can be automated, but scope changes, objections, high-value messages and commercial judgement need human review.

    How do you track quotation conversion?

    Connect quote version and value to stages, buyer engagement, revisions, acceptance, revenue and controlled loss reasons, segmented by comparable deal types.

    Sources and further reading

    Policy and legal material is provided for operational awareness, not legal advice. Verify the current rules and obtain qualified advice for your circumstances.