Agree on the handover before adding tags
Separate the design deliverable from the product data and the sales workflow. Ask the client to approve the SKU list, units and descriptions, and identify the person who will review incoming requests. Agree who maintains the catalog when the range changes.
The current plan model covers one workspace per plan. Do not assume that one subscription supplies isolated client accounts, agency billing or a managed reseller service. Confirm the workspace arrangement in the early access request.
- Approved PDF, including the final page order.
- Product owner responsible for SKU and unit accuracy.
- A sample buyer selection that the client can approve.
- A named workflow for reviewing requests and preparing quotes.
- A maintenance brief for future PDF and product updates.
Build around the client's existing catalog
Upload the approved PDF, add product details manually or through CSV, and place tags near the relevant products. Choose a reader logo and colors that suit the client. Keep tags clear of small print, prices and product details.
Test the catalog on a phone as well as a desktop. A complex printed spread may be difficult to read on a small screen even when the reader itself fits. Check zoom, tag placement and the path from a product to the selection.
Review a real example of the intended inquiry
Choose several representative products with different units. Build a selection with the client, confirm the quantities, and check the resulting request in the workspace before distributing the catalog broadly.
Illustrative agency acceptance brief Catalog: promotional packaging range Selection: 200 bags + 50 boxes Check: correct SKU, unit and page for each product Owner: client's sales coordinator Next step: coordinator prepares a quotation in the client's sales process.
Plan links, QR codes and future editions
A Foluro publication can be shared by link, QR code or an embedded reader. When replacing the PDF within the same catalog, the publication link is retained. This allows an existing printed QR code to lead to the new version.
Page changes still need a content review. Check retained tags, page links and other interactive elements after every replacement. Test password and expiry settings using the same route a client reader will use.
Keep the proposal precise
Offer the workflow you have tested: catalog presentation, product selection, requests in a workspace and email notifications. Paid checkout, customer domain provisioning and automatic CRM synchronization need a separate confirmed implementation.
Use the public demo to show the buyer experience, then include the proposed client workflow in an early access request.