The auction catalog starts with verified donated items

A promised auction item is not ready for your catalog. Give every item one stable ID, then move it through four visible states: promised, received, verified, and published. Create the public auction lot only after your team has the item or certificate and has checked the terms a bidder will need.

That is the core rule for nonprofit auction item tracking: the donated item is the source record; the auction lot is what you build from it.

Keep the donated item separate from the auction lot

An item record answers what a person or business agreed to provide. A lot answers what a bidder can win.

Those are not always one-to-one. A restaurant certificate and two theater tickets may become one evening-out package. A set of four admissions may become two identical lots. One experience may stay as one item and one lot.

Keep the source item ID even after packaging. Current DonorView documentation shows why: its auction workflow can combine several previously recorded in-kind items into one auction item. Your system may use different names, but the relationship should survive. A teammate should be able to open a lot and find every donated item behind it.

When the promise first arrives, record only what you know:

• a stable item ID;
• the donor and the person who secured the commitment;
• a plain description of the promised item or experience;
• the expected delivery method and date;
• any stated restrictions, expiration, or redemption contact; and
• the owner of the next action.

If a business provides the item, keep the business and its current contact connected without treating them as the same donor record. The same organization-and-contact boundary should survive after the event.

Do not fill gaps from memory. A missing certificate, unclear blackout date, or unconfirmed pickup belongs in an exception queue.

Move each item through four observable states

Use states that describe evidence, not optimism.

1. Promised: you have a donor commitment and a next owner, but not the item or usable certificate.
2. Received: the physical item is in a named location, or the digital certificate is accessible from the item record.
3. Verified: someone checked the exact item, description, restrictions, expiration, redemption path, and donor connection.
4. Published: the public lot was created from verified source items, and its lot ID links back to them.

Current auction tools expose some of this evidence directly. Greater Giving's procurement workflow includes status, location, date received, donor, and responsible solicitor, while DonorView documents restrictions, expiration, solicitor, and donor fields on an auction item. Those vendor fields are not a universal schema. They are evidence that a promise, physical receipt, review, and public lot require different facts.

Status names alone are not enough. Add evidence. “Received” needs a storage location, file link, or named custodian. “Verified” needs a reviewer and date. “Published” needs the public lot ID.

Use one catalog-readiness gate

Before a volunteer publishes a lot, require six checks:

1. The item, certificate, or redemption instructions are accessible.
2. The public description matches what was received.
3. Restrictions, blackout dates, and expiration are visible when they affect use.
4. The redemption contact or process has been confirmed.
5. The item remains connected to its donor and internal owner.
6. Every source item in a package is linked to the final lot.

These are practical checks, not invented edge cases. Current 2026 procurement forms from Jack's Basket and Girl Scouts of Western Washington independently ask for combinations of donor details, delivery, restrictions, expiration, and redemption information.

Keep valuation, deductibility, receipting, gaming, and accounting questions outside this readiness gate. Route them through your nonprofit's approved policy and qualified advisers. The item tracker should preserve the source information; it should not make those decisions.

Package items without erasing their history

Suppose one donor provides a restaurant certificate and another provides theater tickets. Keep two item records. Verify each delivery and each set of terms independently. Then create one public lot and link both item IDs to it.

The lot description can present one coherent experience. The internal record should still answer:

• Who provided each component?
• Where is each certificate or item?
• Which terms apply to which component?
• Has each donor follow-up been assigned?

You do not need a particular product or field set. You do need enough evidence that a volunteer can take over without asking which spreadsheet is current.

Hold missing items out of the catalog

Near the publishing deadline, run a view of every promised or received-but-unverified item. Give each row one owner and one next action: obtain the certificate, confirm a restriction, photograph the item, correct the description, package it, or decline it.

Do not publish an item merely because the donor is reliable or the committee expects it to arrive. A smaller catalog of verified lots is easier to run than a larger catalog that creates bidder questions, substitutions, and pickup exceptions.

Once bidding closes, hand the winning lot ID into your auction checkout workflow. Intake proves what can be sold. Checkout proves that the right invoice was paid and the right item was released.

Start fundraising free →