Best Practice: Creating Products in MSP Pulse
Every quote line, every ticket product, every recurring charge and every invoice line for a product in MSP Pulse traces back to one record: a catalogue item. Get that record wrong, with a vague name, a stale price or the wrong billing type, and the error doesn't stay in one place. It turns up months later as a mispriced quote, an invoice line posted to the wrong account, or a margin that was never what you thought.
This guide covers how to create and maintain catalogue items so they hold up over time, and traces how a product moves from the catalogue through a quote, into a ticket or project, and out as an invoice line, so you can see where a bad setup decision will bite.
Labour is not covered here. Billable time is priced from Labour Roles, not from catalogue items, so everything below is about products: hardware, licences, services and similar.
1. Name and identify products so they survive change
Name generically unless the vendor name matters to the client. "Managed Backup" outlives a vendor switch; "Datto Backup" doesn't. Microsoft 365 is a reasonable exception, because the client needs to recognise exactly what they are buying. A backup tool, an AV product or a monitoring agent rarely needs the vendor in the name.
Choose the name carefully, but a rename is safe. An invoice line takes its account from the product it came from, not from its name, so renaming an item doesn't change where its lines post. The name still appears on quotes and invoices, so pick one your clients will recognise.
One catalogue item per product, not per client. It's tempting to clone an item so one client gets a different price. Don't. For a one-off product, you can change the price on that client's quote line while the quote is a draft. For a recurring product, set the client's price when you add it to their agreement's Recurring Items tab. Every duplicate is another place a cost change has to be remembered.
When a vendor reissues a product under a new part number, create a new item and retire the old one. The catalogue has no separate SKU field, so the name and description are all that identify the product. Reusing the old item for a different product blurs what past quotes were for. Create the new item, retire the old one (see Section 6), and let history keep pointing at the old item.
2. Choose category and billing type deliberately
Every product has a Category (required), an optional Sub-category, and a Billing type. Together they decide how the product is filed, which account it posts to, and how it is invoiced.
| Billing type | Use it for | Notes |
|---|---|---|
| One-off | Hardware, cables, one-time fees | Invoiced once through Load Pending |
| Recurring monthly | Monthly licences and services | Must be attached to a billing agreement; see Section 5 |
| Recurring annual | Annual licences, warranties, renewals | Same, on an annual cadence |
Match the billing type to how the client is actually charged, not how you think of the product. A warranty renewed yearly should be an Annual recurring item, not a One-off line you re-add every year. Recurring items billed from an agreement are prorated, so the first invoice lines up with the agreement's cycle without you working it out by hand. The billing type also has to match the agreement's cadence: you can't add a monthly item to an annual agreement.
Mark service categories as services. Each Category has an Is a service setting (Products, Categories tab). Use it for categories like Managed Service, so the catalogue list tells services and goods apart.
Change billing type before the item is in use. Once an item is on quotes or agreements, changing its billing type is far messier than getting it right at the start.
3. Use categories deliberately: they drive accounting, not just browsing
The category you file a product under decides which accounting code its invoice lines post to. MSP Pulse looks for a code in this order, and the first one set wins: the item's own account override, then its Sub-category's account, then its Category's account. If none is set, the line posts to the tenant's default sales account (Settings, Accounting).
That last fallback is the dangerous one. Xero refuses an authorised invoice line with no account, so most tenants set a default, which means a badly filed product doesn't fail visibly. It quietly posts to the generic sales account, and you find out at month end.
Practical guidance:
- Set an account on the Category wherever you can, so every new item filed under it inherits something sensible.
- Use a per-item override only when one product really needs to post differently from the others in its category.
- Keep the Category and Sub-category structure shallow and stable. Reorganising categories after items are in use on agreements is easy to get wrong without noticing.
4. Price with intention
Each item has a Purchase Price (cost) and a Price (the sell price). Fill in both. The item form shows the markup as you type, in money and as a percentage, and turns red if the price is below cost. A sell price with no relationship to what the item costs you is a margin left to chance.
A catalogue price change does not reach existing work. Prices are frozen where they are used: a quote line takes the catalogue price when it is added, a ticket product takes it when it is added, and a recurring item on an agreement keeps the price it was given. So when a vendor reprices something:
- Update the Purchase Price and Price on the catalogue item, for new quotes and tickets.
- Walk the agreements that carry the item and decide, one by one, whether the client's price moves. Nothing updates them for you.
MSP Pulse doesn't alert you when a vendor price changes, so treat a vendor notice as the trigger for that pass. Keeping the Purchase Price current is what makes the markup figure worth looking at.
5. How a product actually flows, end to end
A product can reach billing by two routes.
Through a quote. A catalogue item becomes a quote line. If the quote is won, its products are seeded onto the ticket (one-off and recurring products) or the project (recurring items). A draft or declined quote never reaches billing.
Straight onto a ticket. An engineer can add a catalogue product to a ticket with no quote behind it, the everyday "fitted a cable" case. This works for non-labour products on ordinary tickets only, not on project tickets.
From either route, billable items end up in the same pool that Load Pending draws on to build invoices. Load Pending groups work per client, and a client can come out as more than one invoice, for example when a ticket is billed separately or when agreements have different payment terms. A one-off product is invoiced in the next Load Pending run. A recurring product must be attached to a billing agreement before the ticket it came from can be closed. This is checked in three places: when you close the ticket, in the close confirmation, and as a warning in the time-entry form. Once it is on the agreement, it is billed from there on the agreement's cycle.
6. Keep the catalogue current, not just correct at creation
Retire items instead of deleting them. An item that old quotes, agreements or invoices refer to should keep existing so those records still make sense. Set it to inactive: it drops out of the pickers for new quotes and tickets, and the history is untouched.
Treat a vendor price notice as a task. See Section 4: update the catalogue, then decide agreement by agreement.
Review on a cadence. Look through your recurring items when you review each client's agreement. You are already asking what the client pays for and whether it still makes sense, so it is a natural moment to check that the catalogue items behind it still reflect what you buy and what you charge.
Pre-flight checklist for a new catalogue item
- [ ] Named generically unless the vendor name matters to the client, and named the way you want it to appear on invoices
- [ ] Checked for an existing equivalent item first, so no near-duplicates
- [ ] Billing type matches how the client is actually charged
- [ ] Filed under the right Category (and Sub-category if needed), with an account set on the item, its Sub-category or its Category
- [ ] Purchase Price and Price both filled in, and the markup is the one you intended
- [ ] If recurring: it will need to go onto a billing agreement before its ticket can be closed
- [ ] If it replaces a product under a new part number: created as a new item, and the old one set to inactive