What's on the Shop Ticket PDF

Generate the shop ticket from an open order: click Document Generation at the top right, then select Generate Shop Ticket. Unlike the invoice and receipt, the shop ticket is not generated automatically. You create it when your team is ready to start production.

The shop ticket is an internal Instructions document. It is never shown in the Customer Portal, it shows no pricing, and it is built purely for your production staff. It is usually a two-page document: the order and monument details fill page 1, and the drawing sits on page 2 (the footer reads 1/2, 2/2).

An internal Instructions document

When you generate a shop ticket, MonuDesk downloads the PDF and quietly stores a copy on the order as an Instructions document. Generate it again and the new copy replaces the previous one, so the order keeps a single shop ticket, labelled with its version such as V2. Instructions are always internal: they are never customer-visible and never appear in the Customer Portal.

In the order's documents list, an Instructions document shows a non-interactive Internal status instead of the usual External/Internal toggle, with the tooltip "Instructions are always internal only and never shown in the Customer Portal." There is no way to switch a shop ticket to External.

When you replace an order's monument thumbnail or sketch, that image is also saved into Notes & Files as a Drawing so it flows onto the shop ticket's drawing page. If that save ever fails, you'll see a warning telling you to add the image manually under Notes & Files.

Page 1: order details

The left meta block shows:

• Order Number,

• Issue Date,

• Sales Rep,

• Section / Lot / Space, in bold, followed by the Block and Tier from Cemetery & Logistics when they are filled in (for example A / 12 / 2, Block 4, Tier 1), with one Plot 1:, Plot 2: line each when the order has several plots,

• Payment Status on a priced order: Paid in Full, Partial Balance Due or Full Balance Due,

• Last Payment: the date of the most recent payment, once one is logged,

• Promise Date, when the order has one,

• Cemetery Notes.

The payment and promise rows let the shop floor check whether a job is paid for and when it was promised before releasing the work. On a retail order the cemetery itself is named in the Deliver To block on the right.

On a customer pickup order there is no cemetery to print. The left block carries a Delivery Method row reading Customer Pickup in place of the cemetery rows, and no cemetery map is printed.

For wholesale orders, the left block also carries the full cemetery contact details: Cemetery Contact, Cemetery Phone, and Cemetery Address.

The right block shows two parties:

• Purchaser: the customer placing the order (name, address, phone, email). A contact imported with the city, state and ZIP in separate columns prints the full address.

• Deliver To: where the monument is delivered. The purchase order keeps the heading Ship To.

Who appears under Deliver To depends on whether the order is retail or wholesale:

• Retail: Deliver To is the cemetery (its name, location, phone, and contact), because that's where the monument is installed.

• Wholesale (Monument Company, Funeral Home, or Vendor): Deliver To is the purchaser, and the full cemetery contact details sit in the left meta block instead.

• Customer pickup: Deliver To reads Customer Pickup followed by your office name, or your company name when the order has no office, with that office's address and phone, so the shop floor knows where to stage the stone.

Phone numbers on the ticket print the way they are written in your company's country, for example (239) 049-0234 for a US company or 030 901820 for a German one. A number from another country keeps its country code. Text that is not a valid phone number prints as it was typed.

Item lines

The items table lists each part with Item, Material / Color, Size, Finish, and Qty. Service orders use Service and Description columns instead, and list the pricing inputs under the service's measurements: Letters and Price per Letter for a By Letter Count service, Quantity and Price Each for a By Quantity service. Otherwise no prices are shown. The stone row is labelled with its monument type, so a footstone prints as Footstone and a ledger as Ledger. Dimensions display in the same format you entered them: feet-inches if you typed feet-inches, inches if you typed inches. Sizes can carry part of an inch: a 17.25 inch length prints as 17.25", or as 1-5.25 when the stone is in feet-inches.

A slant can carry a dual height, such as 10/2, typed as free text in its height field. It prints on the shop ticket exactly as you typed it, and the same value is kept on the order overview, the purchase order, the inventory grid and Smart Prefill. Bevels keep their existing 6/4 behaviour.

If the order carries two or more stones or services between them, the rows are grouped under all-caps group bands, so the shop floor can tell each monument and each job apart: STONE A, STONE B, STONE C (just STONE when there is only one stone), and each service under its own name or SERVICE A, SERVICE B (just SERVICE when there is only one). Accessory rows (Vase, Porcelain, Urn, Etching, QR Code, Vault) follow their stone, and accessories added to a service order print on the ticket too. A service-only or accessory-only order prints no stone row.

A Vase row tells the shop which vase to pull. Its material prints with the color on a second line, for example Granite above G633 Import Gray. The Size column shows the vase's size. The Finish column shows the vase style as the app names it, with the finish where the style has one, for example Tapered (All Polish), Tapered (Polish 2) or VA (Veteran).

You can replace those letters with a real name. Hover a stone and click the pencil (its tooltip reads "Rename this stone on documents"), then type a name: Husband's Die, Companion Marker, Section B Flush. The pencil is on the stone pills in the price summary panel of New Quote and the order editor, on the stone tabs on Review & Create, and in the Generate Purchase Order and Generate Foundation Order windows. On a saved order the rename saves straight away. A service takes a name the same way: in New Quote, hover the service on the Service step's service bar and click the pencil.

The name replaces STONE A on the shop ticket's group bands and in its per-stone summary block, and on the quote, invoice, contract and purchase order. On a purchase order the plain STONE A dividers are still left off, because a vendor does not need them, but a name you typed yourself is kept, since it is the only thing telling the vendor which rows belong to which stone. The Foundation Order does not show a stone name at all. Clear the name and the letter comes back.

The foundation is its own line item, but only when the stone actually has a foundation. Foundation Material, at the bottom of the Finish & Polish card on the Items & Configuration step, offers None, Concrete and Granite, and a new stone starts at None. Set it to Concrete or Granite and the line prints with that material and the foundation length × width. A granite foundation also prints its finish in the Finish column, the same finish as the base. A concrete foundation has no finish. Leave it on None and no foundation line is printed at all, so nobody is asked to pour one.

Finishes use short codes: P2, P3 and P5 for polished uprights and S2, S3 and S5 for steeled, plus base codes like PFT / BRP. Two further codes, PFT BRP and STL BRP, can be picked on the base finish slider, on the flat-marker finish slider and in inventory, and they print on the ticket as those trade codes. Flat markers have a finish slider of their own, covering the top and edges only. A per-face breakdown prints in full on the ticket. Only a finish that is neither a recognized short code nor a breakdown MonuDesk can label falls back to a Custom Finish label, and the shop ticket is the only document that still uses those words. Top shapes are labeled too, such as Serp Top, on an upright and on a Slant Marker, whose Top shape is Flat Top or Serp Top.

A stone with a base and a subbase prints as one stacked Die / Base / Sub-base row. Each line of that row shows its own Qty., and the Sub-base line always reads P5 (polished all around). A base with a polished margin carries the width in its finish, for example PFT / BRP ( 1.5" PM ). When your company language is German, the ticket spells every finish out in words instead of a code.

A long item table continues on the next page under a repeated header row.

Order Details box (Quote Highlights)

Below the item lines is a light-blue Order Details box holding the Quote Highlights: the build summary your team needs at a glance. Sizes that already appear in the item lines are not repeated here. The box contains:

• Finishes: the finish per element (for example "Upright: P5", "Base: BRP", or a per-face list like "Upright: F Black | B Black | E Black | T Black").

• Lettering: the lettering style and related options.

• A decedent grid, laid out in two columns when there are two or more decedents. Each decedent has a Decedent N header and the fields Given Names, Surname (with "(both sides)" appended when it applies), Dates (shown as birth – death), Additional Text, and Facing.

The lettering cut list

On a service order with lettering, the shop ticket prints what the engraver is to cut, kept apart from what they must read but leave alone. It comes straight from the Lettering & Inscription card on the Service tab of the Items & Configuration step, so correct a name or a date there and it is corrected on the ticket.

The stone's identity prints first, under a Stone heading in the Order Details block: Family Name, Stone Type, Stone Color, and Other Names on Stone while those names are already on the stone and are not being cut again.

Below it the cut list prints in a bordered box with two columns:

• ENGRAVE THIS, set in larger type, is the work. Each person's Deceased Name, Date of Birth and Date of Death lands here when its Engrave this box is ticked. Family Name joins it only when "The family name also needs cutting" is ticked, and the Inscription needed free text always joins it, printed as Inscription.

• NOTES (DO NOT ENGRAVE), set smaller, is context. Anything left unticked lands here, and Inscription Location always does.

A work order can carry a whole family. With two or more named people every line takes a suffix, so nobody has to guess whose date it is: Deceased Name (Person 1), Date of Death (Person 2), and so on. A one-person job prints without suffixes.

The same grouping is on screen before you print. The order popup's Order Details tab shows a Lettering & Inscription row ("Only lines under Engrave This are cut") split into Stone, ENGRAVE THIS in green and NOTES (DO NOT ENGRAVE) in amber, with the same person suffixes, and the Review & Create step shows the same recap. The row does not appear at all until a lettering field has a value.

Order notes, installation notes and design notes

Below the Quote Highlights, the ticket shows Order notes: (whatever was entered during monument configuration) and Installation Notes: (placement details added during the cemetery step, like which direction the stone should face or where in the plot it goes). Descriptions and notes print exactly as typed, with their line breaks, blank lines and spacing, and a long note runs on to the next page.

Design notes typed in the Sketch & Inscription step print in their own Design Notes block. When every decedent shares the same notes, one block prints; when their notes differ, a block prints per decedent, labeled with the decedent's name — for example Design Notes — Jane Doe.

Page 2: the drawing

The drawing renders on page 1 only if there's room left after the item lines and Quote Highlights; otherwise it moves to its own page 2. That's why a shop ticket is usually two pages. The heading reads Drawing for a single image or Drawings when there are several. Sketches built in the Sketch & Inscription step are treated the same way as uploaded drawings.

Footer branding

Every page ends with your company name in bold above Powered by MonuDesk, centered at the bottom, with the page number (1/2, 2/2) in the bottom-right corner.

Your logo. If you have uploaded a logo, it prints at the top of the shop ticket as well. Upload a company-wide one in Settings → Company Profile, or give a single office its own in Settings → Office Locations, on that location's Logo field. An office's own logo wins, and an office with no logo of its own falls back to your company logo. The same field sets where the logo prints, Left, Center or Right, with a mock document preview showing where it will land; Left shifts the document title across to the right. The same logo prints on every document MonuDesk generates, and with no logo anywhere the ticket prints without one.

For more on why the shop ticket is locked to internal, and how the External/Internal toggle works on other documents, see Internal vs External Documents.

Related articles:

• How to Open an Order

• How to View and Download Documents

• What's on the Invoice PDF

• What's on the Receipt PDF