Sure, you can change them Separately, even.
You control what you see on the screen, and separately, what the customer sees. For instance, you don't need to show them Item, but you need to see it on your screen for managing sales. That might mean that you stock Furnace Motors in various sizes, horsepower and voltage, but all you want the customers to see on their sales is "replacement Furnace Fan" as Description Only, in the Print Preview and Email view.
As for your example, Yes and No. Some of what you show is Header info, some is the Body (the items listing) and then you have some Custom stuff, as well. Let me help in sections:
Header = the SO, the relational database pulls Customer Info, you fill in dates, etc.
Body = Items, qty, rate, etc. This is the Details of their order to be fulfilled. This is part of the relational database = you will select Items.
Requesting agent = Header info. Open help to understand if this is your Sales Rep or their Customer Primary Contact. I don't know what data fills this in for you, but that is two places that would provide this.
Serial Number, in Enterprise, is each Item you sold them. Perhaps you want to use Edit Customer, Payment Settings, their Account Number. Fill it in. In the Program, in the Template, you will add this Header Field to the template, but retitle its Label as Serial Number, for instance, when you repair installed equipment at the customer location. Or, you want a Header Field they fill in while on the job site making a repair, and it varies per work order? See how you can use all of these functions with flexibility?
Oh, and when I use the term Header Field, you use the Layout Designer to drag them anywhere. It isn't required to be "at the top" but "header" means it relates to that Customer and this Sale, not the Items listed but the Overall order itself. Such as PO is Header = this one Order.
Warranty Consideration Y/N? What matters here is what the field's contents are going to be used for, if that is Notational or part of the Relational database. Example: Serial Number on each Line Item I sell you is part of the database if I use Enterprise with the function to track serial numbers. In QB Pro, I Notate it on a custom column in the body of that form. See how tools and functions vary?
Customer Complaint: this is not a Word processing document. But, for instance, let's pretend the first charge item is a service item named "Inspection" and in the Use of the item here, you put a specific and custom description, such as "Check around back of furnace; customer states they are seeing smoke when the fan runs." You have up to 4,095 characters. That isn't its own Block of text; that is part of the item Row in the Body.
You can make text boxes, in layout designer, but that isn't "text I fill in while making the transaction." It's meant for Permanent text you want to have show all the time, such as your business License or an Environmental License that is required on all of your forms. Or, text such as "Please note that this order requires a Prepayment." Or, directions to your location if this is material to be picked up by your customer.
Your Inspection report format is part of either the Form Printing and then hand filled in, on the job site, or it doesn't belong on the QB form at all. Another option is to use an Estimate for that part. Again, some of this would need to be better defined. Example: One Estimate is designed, you list the Visual Inspection service item on it and Memorize it. Make one with the Detail Inspection item on it and memorize it. Now you double-click to Trigger it and use it, like a Worksheet, for a specific customer, preliminary to the actual SO.
In fact, I use an Estimate for my Service Agreement and if you look closely, you can see how it looks like a document, but is filled in from QB as an Estimate.
And on your screen, it doesn't look like you are seeing it. It looks like Create Estimate always looks. A lot of that text is Text Boxes, but the Items or Scope is mine to control and the Customer Info is pulled from Edit Customer and Customer Contact.
Please see my attachment.
