Create the intake trigger
Everything so far describes how a delivery is inspected. The trigger decides when, by linking a document event to the plan and the team. Without one, checks would have to be raised by hand for every delivery.
For tomato intake, the event is the posting of a purchase receipt. At that moment the received lot exists in inventory, which is what the inspection needs: the Brix reading can be written to the lot, and the inspection status that follows from the grade can control whether the stock is allowed to move.
- Select the Search icon
, enter Quality Control Triggers, and then choose the related link. - On the action bar, select New.
- Fill in the fields as follows.
| Field | Value | Why |
|---|---|---|
| Document Type | Purchase Receipt | The delivery arriving from the grower. |
| Document Action | Post | The check is created when the receipt is posted. Select the AssistEdit button to choose from the Quality Control Trigger Actions page. |
| Location Type | All Locations | Tomatoes are inspected wherever they are received. Change to Location and name a Location Code to restrict the trigger to one site. |
| Quality Check Type | Item | The check is about a specific product, not a general activity. |
| Item Type | Item | The trigger applies to one item. |
| No. | The tomato item | Name fills in from the item. Use Item Attribute instead to cover a group of items, or All Items to inspect everything received. |
| Source Type | All Vendors | Every grower's deliveries are inspected. Use Vendor with a Source No. to inspect one grower only. |
| Team | INTAKE | The team whose members can work on the resulting checks. Required. |
| Plan Code | TOMATO | The plan the check is built from. Required. |
| Per Lot | Selected | One check per received lot. |
Per Lot matters more than it looks. A receipt covering three lots of tomatoes produces three checks, one per lot, so each lot gets its own readings, its own grade, its own Brix value, and its own inspection status. Cleared, a single check would cover the whole receipt and the outcome could not be attributed to an individual lot.
Once the receipt is posted, the trigger raises a check for the intake team.
Confirm the plan is ready
Two read-only fields on the trigger report whether the plan behind it is usable:
| Field | Expected value |
|---|---|
| Plan Certified | Yes — set when the plan's Status is Certified |
| Plan Effective | Yes — set because the plan's Effective Date was left blank |
If either is No, revisit the plan: certify it, or check its effective date. A trigger pointing at a plan that is not certified and effective will not produce the checks you expect.
If the inspection must finish before the receipt is posted
The trigger above inspects stock that has already been received. The alternative is to inspect before the goods are accepted: set Document Action to Create so the check is raised when the receipt is created, and select Finished Before Posting Doc so the receipt cannot be posted until every check it raised is completed or deleted.
That ordering keeps unapproved stock out of inventory entirely, but the lot does not exist in inventory while the check is open, so the inspection status has nothing to block yet. Which approach fits depends on whether your process quarantines received stock or holds it at the door.
For more information, see Set up quality control triggers and Create checks from triggers.
Next step: Complete the first inspection