Manage the people who receive food parcels from your food bank, including their demographics, referrer links, and login accounts.
In HelpingHand, customers are called Recipients. You will find them under Recipient > Recipients in the sidebar. Each recipient belongs to a single customer group. The system tracks their personal details and order history. Address, family size, ethnicity, and referrer relationship are optional fields that your food bank can choose to enable or disable.
You only see your own food bank's recipients -- those that belong to customer groups linked to your food bank.
A recipient record stores:
Customer groups organise recipients within your food bank. Your food bank has one or more customer groups, and each recipient belongs to exactly one group. Groups can also set default order limits (max orders in a period, period length in weeks) that apply to all recipients in that group unless overridden at the recipient level.
Groups are managed under Recipient > Groups in the sidebar.
A shop user is the login account that lets a recipient sign in to the online shop. The relationship is many-to-one: multiple recipients can share the same shop user account. This is useful when a single person receives parcels from more than one food bank.
Each shop user has:
Admins can prevent login (soft-delete the shop user) or reinstate login (restore the shop user) from the recipient detail page. This does not delete the recipient record itself.
Recipients are linked to referrers through auth codes. The flow works as follows:
Recipients use soft delete. When you delete a recipient, the system sets a deletedAt timestamp rather than removing the record. Soft-deleted recipients do not appear in the grid or in shop operations. The delete button appears on both the recipient edit page and the detail page, with a confirmation prompt.
Shop user accounts can also be soft-deleted and restored independently. This lets you block a recipient's login without removing their data.
Navigate to Recipient > Recipients. The grid displays:
| Column | Description | |---|---| | First Name | Sortable. | | Last Name | Sortable. | | Email | Sortable. Links to the recipient detail page. | | Referrer Code | The full auth code (prefix + suffix). | | Referrer | The referrer organisation name. | | Referrer Contact | The referrer contact's name. | | Registration Date | When the recipient registered. Sortable. | | Status | Two icons: enabled (tick or cross) and verified (tick or cross). Guest recipients show a spy icon. |
The grid defaults to 200 rows per page, sorted by first name ascending.
Expand the Filters panel to narrow results:
Each row has three action buttons:
There is no "Create" button on the grid. Recipients register themselves through the shop front or are created via the API.
The detail page shows all recipient information in read-only sections:
From the detail page, admins can:
The edit form lets you modify all recipient fields. It includes additional sections:
The recipient list is filtered so you only see your own food bank's data:
Soft-deleted recipients (those with a deletedAt value) are always excluded from the grid.
Why is the page called "Recipients" instead of "Customers"? HelpingHand uses the term "Recipients" in the admin interface because food bank users receive food parcels rather than purchasing products. Internally, the system still uses the Sylius "Customer" entity.
Can I create a new recipient from the admin? No. The grid does not have a Create button. Recipients register themselves through the shop front or are created via the API. This ensures they go through the proper registration flow, including agreeing to terms and entering an auth code.
What happens when I delete a recipient? The recipient is soft-deleted. Their record stays in the database but no longer appears in the grid or shop. Their order history is preserved. You cannot undo a soft delete from the admin interface for the recipient record itself, but shop user logins can be reinstated.
Can a recipient belong to multiple food banks? A recipient record belongs to one customer group and therefore one food bank. However, the same person can have multiple recipient records (one per food bank) sharing the same shop user login account.
What are order limits? Order limits control how many orders a recipient can place within a time period. These can be set at three levels (highest priority first): the individual recipient, the customer group, or your food bank's settings. A recipient-level override takes precedence over the group default.
How does the auth code work? Each auth code is a unique 8-digit number. Recipients enter this code during registration to gain access to the system. The code also associates the recipient with the referrer and referrer contact who issued it.
What do the status icons mean? The Status column shows two icons side by side. The first indicates whether the shop user account is enabled (green tick) or disabled (grey cross). The second indicates whether the email is verified (green tick) or unverified (grey cross). If the recipient has no shop user, a spy icon appears instead, indicating a guest.