Dad’s Printing / Production / System 05 of 06
2023Recorded work
Partner
Supplier purchase-order coordination
Gather supplier availability, price and timing so the team can choose how to source each order’s materials.
- Noah’s contribution
- Noah describes setting up generated PO forms and supplier email coordination; a separate handoff shows PO link, folder and draft-email mapping changes.
- Historical stage
- Explicitly named retrospective implementation account; supporting PO configuration walkthrough has unfinished delivery details.
- Part of the business
- Dad’s Printing overview ↗
- Make / Integromat
- Purchase-order forms
- Zoho
- Monday
- Google Drive
Inside this system
The workflow
The handoffs
inside the work.
Follow the main path and its branches. Select a step for context; the account below explains what was built, tested or planned.
- Material and quantity requirement
Define the apparel material, quantity and required turnaround for the order. - Generated purchase-order form
Prepare the supplier-facing purchase information in a reusable document. - Supplier availability queries
Distribute questions about available stock, price and timing to candidate suppliers. - Supplier responses
Bring availability, quoted pricing, timing and quantity discounts together. - Purchasing team compares options
Weigh supply, cost and timing rather than treating lowest price as the only criterion. - Order-linked purchasing handoff
Keep the selected purchase information connected to the order and supplier correspondence.
Key records
The information
that carries forward.
| Record | Information | Purpose |
|---|---|---|
| Purchase-order form | Order/material request and supplier-facing purchase information. | Present the requirement in a reusable document. |
| Supplier response | Availability, quoted price and turnaround. | Support comparison under a delivery requirement. |
| Document/folder reference | Stored folder URL, derived folder ID and document web-view link. | Connect the PO resource to the internal order and correspondence. |
Inside the system / 01
Procurement as part of the production handoff
Face-mask supply was scarce. Dad’s Printing needed to know which suppliers had suitable blanks, what they would charge and whether they could deliver in time.
Noah set up purchase-order forms and supplier emails that asked about availability, price and turnaround. The purchasing information also considered bulk discounts.
Inside the system / 02
Turn a requirement into comparable information
The process begins with a requirement that can be represented in a purchase-order form. Supplier queries then gather several decision inputs instead of treating the lowest price as the entire decision: the supplier must have the material and be able to deliver in time. Quantity discounts can affect the comparison.
Noah set up the described automation, while the purchasing team retained the decision-making role. Generated correspondence and comparisons supported that work; the account does not establish autonomous supplier selection or spending approval.
Inside the system / 03
The document must remain connected to the order
A separate historical PO configuration handoff explains deriving a folder ID from a URL stored in Monday, mapping folder and file references, and using a document web-view link. Noah also configures conditional due-date text and draft email fields. These details show the maintenance work needed to keep a generated document connected to its operational record.
Template layout, recipient, order-number convention and folder-sharing decisions still needed confirmation. The handoff shows configuration work, with final generation and delivery testing not demonstrated.
The distinction between a file reference and a folder reference matters here. Deriving the folder ID from the stored URL allows the workflow to address the intended resource, while a web-view link gives the teammate a usable document destination. Neither technical mapping proves that the final recipient can access that resource; the sharing decision was still open.
Inside the system / 04
Versions and neighboring workflows
Named retrospective accounts discuss Zoho and Monday, while other Dad’s Printing material covers Pipedrive and Asana. These represent different versions or periods. The shared business responsibility was carrying purchasing information into the production handoff.
The same accounts describe shipping option and package-size calculations, printed order sheets and barcode status updates. Those provide fulfillment context but do not need to become an extra unsupported procurement subsystem. Shipping calculations are narrated historical implementations, not a verified optimization guarantee, and the PDF template record has its own explicit rendering and integration limits.
Inside the system / 05
Results and remaining work
Generated forms and supplier correspondence kept supply, price and timing connected to the purchase requirement. The records provide no current execution test, measured purchasing saving or verified purchase-order count.
The established scope is supplier correspondence and purchase-order coordination. Automatic stock replenishment and inventory forecasting are not demonstrated in the directly attributed material.
Within Dad’s Printing