Shopify to PandaDoc: Proposals from Orders with Make.com

Introduction

If you still copy Shopify order details into PandaDoc templates by hand, you know the friction. You need to pull order data, map it into merge fields, ensure line items render correctly, then send the document for signature. Small mistakes cost time and slow down revenue workflows. The pattern below shows how to wire Shopify to PandaDoc with Make.com, so every new order can produce a professional proposal with minimal manual touch. Along the way you get a clean audit trail and reliable upserts back into your systems.

To see how this pattern fits into broader automation work, check our Shopify to BigQuery and Slack digest guide and other cross platform approaches we commonly use at Olmec Dynamics. For example our pattern Shopify to BigQuery + Slack digest demonstrates the general approach and how to link a reporting layer back into collaboration channels.

What You'll Need

• Shopify store with API access to orders and a PandaDoc-ready template that contains merge fields for client data and line items
• PandaDoc account with templates that have merge fields matching your data model
• Make.com account with connections to Shopify, PandaDoc, and whatever system you want to write results to (for audit you can use Google Sheets or Notion)
• A clear mapping plan from Shopify order fields to PandaDoc template fields (for example client name, address, line item list, totals)
• Optional: a forwarding channel in Slack or a sign-off step if you want signature routing to a team

Note on plans: for a production scenario you will benefit from a paid Make.com plan to handle multiple steps, error handling, and higher volumes.

How It Works (The Logic)

Trigger: a new Shopify order creates or updates and you decide it should generate a PandaDoc proposal. Make.com reads the order payload, maps the fields to PandaDoc merge fields, creates the document from the template, and optionally sends it for signature. Once PandaDoc returns a document id or a view link, you store that in a downstream system (for example a Google Sheet audit log or back into Shopify as a reference). This keeps a clean, auditable trail for both internal teams and customers.

Why this works well: PandaDoc templates give you a consistent, branded document, while Make.com acts as the glue between Shopify data and the PandaDoc API. You can also add a sign-off path and post a compact notification to Slack or Teams when a document is created and sent.

Step-by-Step Setup

1. Create or locate your PandaDoc template

• Ensure your template includes the common fields you want to fill from Shopify, such as client name, company, address, line items, totals, and a signature section.
• Note the template ID or UUID; you will reference this in Make.com.

2. Prepare your Shopify data map

• Decide which fields you will pull from the order, for example: order number, customer name, customer email, billing address, line items (sku, quantity, price), total, currency, and any discounts or taxes.
• Create a mapping plan that aligns each Shopify field with a PandaDoc merge field. If a field is optional, plan a default value for empty inputs to avoid blank documents.

3. Build the Make.com scenario

• Module 1: Shopify, trigger for new orders or updated orders that should generate a proposal

• Module 2: Data transformation

  • Map Shopify fields to variables for the PandaDoc merge fields. Build a printable line item block if your template uses a table of items
  • Normalize currency and dates to suit PandaDoc formatting

• Module 3: PandaDoc Create Document from Template

  • Template UUID: the PandaDoc template you prepared
  • Name: a descriptive title such as "Proposal for {Company} — {OrderNumber}"
  • Recipients: map the client email and name into the template recipient fields
  • Fields: pass a JSON payload mapping your template placeholders to the Shopify data (for example client_name, client_email, line_items, total_amount, currency, due_date)

• Module 4: Optional Send for Signature

  • If you want PandaDoc to handle signature in the same run, call the Send Document action and ensure recipients are set to the right signers.

• Module 5: Audit log write back

  • Write the PandaDoc documentId and the document URL into an audit log (Google Sheets or Notion) so you can reference the file later and report on adoption and performance.

• Module 6: Slack/Teams notification (optional)

  • Post a short message with a link to the PandaDoc draft and the order details. Keep it concise to avoid noise in channels.

• Module 7: Error handling

  • Add an error path that posts to an ops channel and logs the error in your audit log. Implement a couple of retries for transient API failures.

4. Test thoroughly

• Run a handful of orders through the workflow to verify mapping accuracy and template rendering. Check that the PandaDoc document has all the expected fields with the correct values and that the resulting document URL is stored in your audit log.
• Test a no-data scenario to ensure the scenario handles missing fields gracefully without failing.

5. Go live and monitor

• Enable the scenario and monitor the first 20–50 runs. Look for misaligned fields or missing data and adjust your mapping as needed.

Real-World Business Scenario

A mid-size eCommerce retailer used this exact flow to generate order-based proposals. When an order reached the quote stage, Make.com retrieved the order data, populated the PandaDoc proposal, and stored the PandaDoc document id back into a Google Sheets audit log. The sales team could reference the document link directly from the order and send the proposal with one click. The result was a faster quote cycle and a clean, auditable trail for compliance.

If you want to see similar patterns for other document generation workflows, you can read our guide on generating PDFs from Google Docs and emailing them with Make.com, which provides a complementary approach to document templating and delivery. See Generate a PDF from a Google Docs Template Using Make.com and Gmail.

Common Variations

• Add a signature routing step: route proposals to a sales manager for quick approval before sending the PandaDoc envelope to the client.
• Extend with CRM enrichment: enrich Shopify order data with customer company data and attach to PandaDoc fields for a richer proposal.
• Create an automated follow up: once PandaDoc signature is complete, post a Slack message and update your CRM to reflect the status.

Closing notes

You now have a practical and scalable pattern to turn Shopify orders into PandaDoc proposals using Make.com. The workflow yields consistent, branded documents, an auditable trail, and a smooth handoff to signature workflows if you need them. If you want hands-on help implementing this exact flow or extending it to cover more edge cases, Olmec Dynamics can design and run these automations for your team. See our services and approach at Olmec Dynamics.

If you want to explore related patterns, we have useful guides on bridging Shopify with data pipelines and collaboration tools, such as Shopify to BigQuery + Slack digest and Shopify to ShipStation + Monday.com integration. These patterns can be combined to build end-to-end flows that cover data, ops, and delivery in one connected automation.

Tools Domains

• Shopify: shopify.com
• PandaDoc: pandadoc.com
• Make.com: make.com