ERPNext items: 2 settings and a readiness check

Key takeaways

• Set the maximum discount to match your shop policy.
• Check exempt items against the correct tax account and rate.
• Confirm each item's name, price, grouping and readiness.
• Test the sale and compare the result with what you expected.

If you run a shop on ERPNext, you probably spent real time setting up your items: names, groups, prices, and the details that make the catalog usable. It is easy to treat that work as finished once the first product is saved. The till is where those settings actually get tested. A cashier ringing up a sale is trusting that the item record says what the shop allows, and that the sale follows those rules without anyone having to remember them.

This post covers two item settings and a readiness check before you open for business, or before you hand the till to someone new. Your setup may need more than these three checks. Each one, though, sits at a common point of friction at the counter: how far the price can come down, how tax is handled, and whether the item is ready to be sold at all.

Where the ERPNext item documentation describes a rule, we link to it so you can read the full context. Your version and settings may differ, so use this as a checklist to verify against your own system.

Why item settings matter at the till

An item record is a set of promises. It says what the product is called, how it is priced, whether it is taxed, and what limits apply when someone sells it. The sales screen does not know your intentions. It knows what is stored on the record and what the person at the counter enters.

That gap can lead to mistakes. A cashier offers a little extra off something that was never meant to be discounted. A tax-exempt product gets charged the standard rate because the exemption was never recorded. A product still being set up turns up in a search and gets sold before its price is confirmed. None of these is dramatic on its own, but together they cost margin, create refund work, and leave reports that do not match the shelf.

The fix is not to make every cashier memorize exceptions. Put the rules on the item, check them once, and test how they affect a sale. Memory does not replace that check.

Before you start, gather three things: your product list, the discount and tax policy you actually follow, and someone who can test a sale from start to finish. A setting that looks right on the form may behave differently when someone rings it up, so plan to test, not just review.

Setting 1: Set a maximum discount for the item

The first setting is the discount limit. Most shops have a discount policy, even an informal one. Staff may be allowed to take ten percent off a damaged box but never off a premium product. Loyalty customers may get a little more room, while certain categories stay at fixed prices. Whatever your policy is, it should live on the item, not only in a cashier's head.

ERPNext's item documentation covers this kind of cap. As the Frappe item guide puts it: "Eg: if you set 20%, you cannot sell this item with a discount greater than 20%." The number you enter becomes the ceiling for discounts on that item.

That helps in two ways. It takes a judgment call away from the counter, so a busy or newly hired cashier does not have to decide whether a discount is allowed. And it makes the policy visible. When an owner asks why a sale looked the way it did, the answer is on the record.

Go through your catalog with one question for each product: what is the most we would ever discount this? For many items the answer will be the same across the shop. For others it will be zero. Be honest with the number. A cap that is too generous invites the discounts you were trying to stop, and one that is too tight will push staff toward workarounds.

Set the limits before you open the till for the day, and check high-value items individually. Do not assume old rules carried over if you migrated from another system. Also remember what the cap does not do. It limits discounts on the item. It does not replace an approval process for special cases. Decide in advance how exceptions are approved and recorded.

Think about who is allowed to go past the cap, too. If your setup lets someone override it, decide who that is and write down where the approval is kept. Otherwise the cap is advice, not a rule.

Then test it. Ring up the item at the maximum allowed discount and confirm the sale goes through. Then try a little more and check that the till does not accept it. A rule you have never seen fail is a rule you do not yet trust.

Illustrative example: Test a discount cap

For an illustrative test, set a 20% discount cap on an item. The first is at the cap; the second exceeds it. Compare what the till allows with the limit you entered, and resolve any mismatch before selling the item.

Setting 2: Mark tax-exempt items correctly

The second setting is tax. Many shops sell taxable and exempt items side by side, and mistakes here are common. An exempt item charged the standard rate overcharges the customer and creates a correction later. A taxable item marked exempt undercharges and leaves a gap in your books.

ERPNext handles this through the tax table on the item. The item documentation gives a worked example worth reading closely: "For example, if you have a tax Account, “VAT 14%” and this particular Item is exempted from tax, then you select “VAT 14%” in the first column, and set “0” as the tax rate in the second column."

Read that carefully, because the logic is easy to misread. You are not deleting the tax account or inventing an exempt account for the product. You name the tax that normally applies in the first column, then enter the item's own rate, zero in the example, in the second. The account stays in place for every other item, and the exception sits on the product that needs it.

Do not rely on a cashier to remember that an item is exempt. If the sales screen shows the standard rate on a product you expected to be exempt, stop and fix the record before the next sale.

Start by sorting your items into groups: fully taxable at the standard rate, exempt, and anything on a different rate. The last group is the easiest to forget, so write down the rule for each product. Check those rules against the tax obligations your business actually has. If you are unsure which products qualify for an exemption where you operate, ask your accountant or tax authority before you change the system. This post explains where the setting lives. It does not decide which products are exempt in your jurisdiction. Use the shop sales tax checks when reviewing your wider register setup.

After you set an item, check the result on the sales screen. Add it to a test sale and read the tax line. It should show the rate you intended, and the total should reflect it. Then add a taxable item to the same test sale so you can see both behaviors side by side. A mixed test catches problems that a single-item test misses.

Tax also shows up in reporting. If tax totals look wrong at month end, item settings are one of the first places to look. Clear marking of exempt items makes that reconciliation much easier, because you will not have to work backward to see why a total is off.

Finally, write down why each exemption exists. A short note on the item, or in your procedures, saves time when a new team member asks, or when an inspector does. The setting tells the system what to do. The note tells people why.

Check 3: Make sure the item is ready to sell

The third check is a question: is this item ready to sell? It is easy to create an item for a product you have ordered but not received, or a bundle you have not finished pricing. An unfinished item creates a risk of selling something you are not yet ready to hand over; check how your setup handles it.

Treat readiness as part of setup. Before an item goes live, confirm the basics. The name should be clear enough that a cashier recognizes the product at a glance. The unit of measure should match how you actually sell it. The price should be the one you intend to charge. The item should sit in the group you expect, so that searches and reports make sense. None of these is exotic, but each is easy to skip when you are in a hurry.

Separate finished items from items still in progress. Some shops use a status field or a naming convention for drafts. Others keep a separate list of products to add later. Pick one method and use it every time. The goal is that a cashier never has to guess whether an item is for sale. If the answer is not clear from the item itself, the item is not ready.

Review the sales-related settings on each new item too. Compare each one with how you really use the product. An item you only buy in should not be set up as something you sell. Settings like these are easy to set once and forget, so agree on what each one should be with your team instead of copying an example you found online.

Keep the active catalog short. Review items you no longer carry so staff can distinguish them from products still for sale. Check how your setup handles discontinued products before choosing a way to remove them from daily use.

Finally, consider photos and descriptions if your staff rely on them. A cashier who can see a product image may catch a wrong item before it is rung up. Even when the till does not display images, a clear record helps staff who look items up on a tablet or second screen.

Common mistakes to watch for

A few patterns show up again and again in small shops. Knowing them helps you look in the right place when something goes wrong.

The first is the copied item. When a new product resembles an existing one, it is tempting to duplicate the old record and change the name. Before relying on a copy, check its discount cap and tax row against the new product's rules. Before saving a copy, read through each setting on the new record as if you were creating it from scratch.

The second is the one-time fix. A price or tax rate gets corrected for a single sale, and the item record is left alone. The next sale repeats the error. If an exception happens twice, investigate whether the record needs correcting or the sale needs separate approval.

The third is the silent default. A field left at its starting value looks like a decision, but it is not one. Walk through the item form and make an explicit choice for each setting that matters to sales, even when the default happens to be what you want. Then you know it was checked.

The fourth is the forgotten test. Settings get changed in a rush before a busy weekend, and nobody rings up a sale afterward. Build the test into the change itself, so that no update is finished until a sale has been run against it.

The fifth is the unclear owner. When nobody is responsible for item settings, everyone assumes someone else checked them. Name one person who approves changes, even if others are allowed to make them.

Test a sale before you trust the settings

Setting values on a form is only half the job. The real question is whether the till follows them. A simple test plan helps catch problems before a customer does.

Start with one sale for each rule. Take an item with a discount cap and try to exceed it. Take an exempt item and check its tax line. Take an item that is not ready and check whether the till allows it to be sold. Write down what you expected and what happened. If they differ, fix the item or the process before you go on.

Then run a mixed sale. Put a discounted taxable item, an exempt item, and a normal item in one basket, and check each line and the total. For a closer review, use the item tax sale-line checks.

Test with the people who will work the counter. A manager may know the policy by heart, but a new cashier will hit the edge cases. Watch them work through a sale and note where they hesitate. A pause at the counter often points to a setting that is unclear or a policy nobody has written down.

Repeat the test after any change. Updating an item, changing a tax setup, or revising a discount policy can affect sales that were correct the week before. Keep a short script with your setup notes, covering the outcomes your shop needs to check.

Check the reports the next day, too. Confirm that the discount, the tax, and the item appear where you expect them. If the till looks right but the report does not, the problem may be in how the sale was recorded or how items are grouped. It is better to find that on a quiet day than at month end.

Keep the process going

Item settings are not a one-time job. Products, suppliers, and policies change. Assign someone to review each new item, and schedule a short review of the full catalog a few times a year. Keep it simple enough that it actually happens. Use a one-page checklist and allow time to follow up on anything that fails.

Make sure the people who set up items talk to the people who ring them up. A discount cap that looks sensible in the back office can break the flow at the counter. A short conversation prevents a lot of rework.

Start with one item today

Choose one item and compare its discount cap and tax row with your shop policy. Confirm its price and readiness, then run a test sale and record any mismatch to fix before selling it.

Related guides: Card surcharge rules: 6 checks before you ring a sale · Stockroom ladder setup: 6 checks before a count.

Common questions

Does this cover three ERPNext settings?

No: it covers two item settings and a separate readiness check. The third check reviews whether the product information and your sales process are prepared for a sale.

Does marking an item exempt decide its tax status?

No: the setting records the tax treatment you have determined applies. Ask your accountant or tax authority if you are unsure whether an exemption applies.

What should happen when a test fails?

Resolve the mismatch before selling the item. Check both the item record and the process staff use at the till.

General information, not legal or tax advice.