In short and in plain language
Companies often send gifts to customers at the end of the year. One buyer then orders for many people at once. Each gift goes to a different address.
A normal shop sends one order to one address only. So the shop needs a list. The list names each person with an address and a short note. The shop checks the list before anyone orders.
Then the system for stock and bills splits the order. Each person gets their own parcel. The buyer gets just one bill. It shows what each gift cost. The buyer needs this for tax.
The addresses belong to other people. The shop keeps only what it needs to deliver. After that, it deletes the list. The free version of Shopware cannot do all this by itself. We build it for you.
In November, many companies order gifts for customers and business partners: a gift basket, a bottle of wine with a card, a promotional item with a logo. For the wholesaler supplying these goods, this is rarely a normal order. The buyer sends a spreadsheet with dozens of recipients, each with their own address and their own greeting, and the sales office types the lines into the ERP by hand. The B2B shop is left out because its checkout expects one delivery address per order. This article shows how to bring corporate gifts with many delivery addresses into the shop cleanly: with a recipient list as a template in the customer portal, an address check before submission, splitting into partial shipments in the ERP and a collective invoice that shows the value per recipient. That last point is more than a convenience for your customers, because German income tax law attaches a value limit per recipient and a recording obligation to gifts for business partners. This article is not tax advice. It shows which information the shop can provide for it.
Key takeaways
- The standard checkout in Shopware CE builds one delivery from all line items to the selected delivery address (Shopware source code). Gifts for many recipients therefore need a separate ordering path with a recipient list.
- A recipient list as a template in the customer portal replaces the spreadsheet sent by email. The shop checks mandatory fields, postcode per country, duplicates and greeting length line by line before the buyer submits.
- Depending on the ERP, the bulk order goes over as one order with a recipient list, as one delivery per recipient or as individual orders with a shared reference. Tracking number and status flow back to the portal per recipient.
- An invoice may consist of several documents if one of them states the total consideration and tax and refers to the others (Section 31(1) UStDV). This turns the recipient list with value per recipient into an attachment to the collective invoice.
- Gifts to business partners are only deductible if they do not exceed 50 euros in total per recipient and financial year (Section 4(5) sentence 1 no. 1 EStG), and they must be recorded individually and separately (Section 4(7) EStG).
- Delete the working list with recipient data after delivery (Article 5(1)(e) GDPR), while the invoice and its attachment are kept for eight years (Section 14b(1) UStG).
Why corporate gifts break the standard checkout
A gift for a business partner is an ordinary item in the shop: a gift basket, a bottle in a wooden box, an embossed notebook. What is unusual is the order. The buyer pays once, but the goods go to many addresses, mostly to companies, sometimes directly to individual contacts, each shipment with its own card. In food and beverage wholesale, among promotional goods suppliers and packaging suppliers, this demand arrives within a few weeks, exactly when warehouse and shipping already have plenty to do at the end of the year.
The standard checkout in Shopware CE is not built for this case. The cart source code builds one single delivery from all line items, and its target is the delivery address the customer selected at checkout (Shopware source code). The developer documentation accordingly describes a delivery in the cart as a shipment with a date, a method, a target location and the line items shipped together (Shopware documentation). In the administration, the order later shows the delivery details with one delivery address, which the merchant can also change there (Shopware documentation). The address book in the customer account helps only to a point: the customer can store and manage several addresses there (Shopware documentation), but selects one of them at checkout.
Creating a separate order for each recipient means dozens of checkouts, dozens of order confirmations and dozens of invoices for the buyer, which their accounting team then has to gather again. So the order ends up where it usually ends up, as a spreadsheet in the inbox. This is not a fringe case. Bitkom surveyed 505 companies from wholesale, retail and motor vehicle trade with at least ten employees (Bitkom). Of the companies with online sales, 97 percent run their own web shop (Bitkom), and 89 percent accept orders by email (Bitkom). Both channels run side by side. With bulk orders to many addresses, the email route produces typical errors: lines are copied twice, postcodes lose their leading zero in the spreadsheet, and a greeting ends up with the wrong recipient.
The answer is not a second checkout but a separate ordering path for bulk orders. It consists of four building blocks, described in the following sections: the recipient list, the address check, the split into shipments and the collective invoice. How such an ordering path sits next to the normal cart without overloading it is covered in our article on B2B checkout optimization.
The recipient list as a template in the customer portal
The core is a template that the buyer downloads in the B2B customer portal, fills in and uploads again. A template with fixed columns takes the randomness out of the spreadsheet: each row is one recipient, each column has a meaning, and the shop can read the file without rework. For small quantities, an input form in the portal is enough, where the buyer enters recipients line by line. For larger lists, the upload is faster, because in many companies the addresses already sit in a spreadsheet or in the CRM.
| Template column | Required | What it is for |
|---|---|---|
| Recipient name | included | Delivery and salutation on the card |
| Company | not included | Business address and assignment in the invoice attachment |
| Street and house number | included | Delivery; a separate house number field makes checking easier |
| Postcode, city, country | included | Format check per country and check of the delivery area |
| Item or gift set | included | Which gift the recipient receives, which may differ per row |
| Greeting | not included | Text for the card, within the character limit of the printed card |
| Internal reference | not included | Cost center or project of the buyer for their accounting |
| Recipient ID | not included | Recognize the same person across several orders in one year |
Three details decide whether the upload works in everyday use. First, character encoding: the shop should read the file as UTF-8, otherwise umlauts in names and greetings turn into question marks. Second, the postcode: it belongs in the template as text, not as a number, so that the leading zero of postcodes in Dresden or Leipzig survives. Third, the greeting: the template states the character limit of the card, and the shop checks it during upload instead of the text being cut off at the print shop. How upload and item numbers work together for normal repeat orders is described in our article on quick order and order lists.
It also matters who may upload the list. In company accounts with several users, the order is often placed by the management assistant or the marketing team, while purchasing approves the cost. The bulk order therefore belongs in the same approval path as any other order above a value threshold; our article on approval workflows and budgets shows what that looks like. If the customer still sends the list by email, the sales office uploads it on their behalf, and the order stays visible in the customer account. The procedure is described in our article Ordering on behalf of the customer.
Address check before the order is placed
An error in the recipient list costs many times more after shipping than it would have cost before: the parcel comes back, fresh goods in a gift basket may spoil, and the customer asks why their business partner received nothing. That is why the shop checks the complete list before the buyer submits it and shows the result row by row.
Shopware CE already covers part of this. In the country settings, the postcode can be made a mandatory field and checked for the correct number of digits and format (Shopware documentation). For custom rules, the field accepts a regular expression (Shopware documentation). These rules apply during registration and address entry. An extension for the recipient list should reuse the same rules per country instead of maintaining its own. That way, the customer account and the bulk order apply the same check, and a change to the country settings takes effect in both places.
- Mandatory fields: name, street with house number, postcode, city and country are filled in every row.
- Postcode in the format of the country and with its leading zero; the country lies within the delivery area of the shop.
- Duplicates: the same address or the same name twice in the list, flagged instead of silently merged.
- Availability per row: item and quantity are available, chilled or fragile goods do not go to parcel lockers or PO boxes.
- Greeting within the character limit of the card and only with characters the card printer can render.
- Summary before submission: number of recipients and shipments, goods value and shipping costs of the whole order.
The buyer corrects faulty rows directly in the portal or uploads a new version. The order is only submitted once all rows have passed or the buyer deliberately holds back individual rows. Checking against an address directory whether the street and house number actually exist goes beyond the format check. It can be connected if your shipping provider or your ERP already offers such a check. It then runs over the existing integration rather than through an additional service in the shop.
One order, many shipments: three data models
Behind the upload lies an architecture question: what exactly is the order in the shop? Three models are possible, and which one fits depends mainly on the ERP. The Shopware data model is less restrictive here than the checkout. An order holds its deliveries as a collection, not as a single value (Shopware source code). The standard checkout puts one delivery into that collection; an extension can create several, one per recipient with its own address and its own status. Whether that is the right path depends on who creates the shipments in the end: the shop or the ERP.
| Criterion | Bulk order with recipient list | One order with a delivery per recipient | Individual orders with a shared reference |
|---|---|---|---|
| What the shop creates | one order, with the checked list attached | one order with one delivery per recipient | one order per recipient, linked by a shared reference |
| Who creates the shipments | the ERP, from the list | the shop; the ERP takes over the deliveries | the ERP, per order |
| Status per recipient in the portal | if the ERP reports status and tracking number back | yes, on the delivery | yes, on the individual order |
| Invoice | one collective invoice | one collective invoice | collective invoice only if the ERP combines orders |
| Canceling one recipient | in the ERP | on the delivery, order value recalculated | cancel the individual order |
| Effort in Shopware | low to medium | high, affects checkout, shipping costs and order view | medium, many orders in the customer account |
If your ERP supports different ship-to parties per delivery note, the bulk order with a recipient list is usually the leanest route: the shop accepts the checked list, the ERP creates the delivery notes from it, and the shop shows the feedback. If the ERP can only hold one delivery address per order, individual orders with a shared reference are the pragmatic solution, as long as the invoice is still collective. The variant with several deliveries in one Shopware order pays off mainly when the shop itself creates shipping labels or no ERP manages the shipments.
Partial shipments in the ERP and tracking per recipient
In the ERP, the bulk order turns into one partial shipment per recipient: a delivery note with its own address, its own card and the items for that recipient. The delivery note carries no prices, because it sits in the parcel at the business partner, not with the buyer. The sender on the parcel is usually the supplier, the card names the giver. Whether the parcel should also carry the name of the buyer is set by the buyer in the order, provided your shipping process supports it.
For the ERP to create the shipments correctly, the handover from the shop needs more than one delivery address: per recipient a unique line number, the address, the line items, the greeting and the buyer's internal reference. Delivery note number, tracking number and status go back to the shop per recipient. A data example with placeholders shows the structure:
{
"bulkOrder": "SB-10087",
"customerReference": "CC 4100 gifts business partners",
"recipients": [
{
"line": 1,
"recipientId": "E-001",
"name": "Recipient 1",
"company": "Client A",
"address": { "street": "<street and number>", "zip": "<postcode>", "city": "Hannover", "country": "DE" },
"items": [ { "sku": "GIFT-M", "quantity": 1 } ],
"greeting": "Many thanks for the good cooperation."
}
]
}
// Feedback from the ERP per recipient
{ "bulkOrder": "SB-10087", "line": 1, "deliveryNote": "<delivery note>", "trackingNumber": "<tracking number>", "status": "shipped" }In the customer portal, the buyer then sees their recipients with a status per row: in preparation, shipped, delivered or returned. The last status matters most. If a parcel comes back as undeliverable, the buyer needs a message with the affected row and a way to submit a corrected address. Without that feedback, they only find out when the business partner says thank you, or does not.
One point that is easily missed in the calculation: every partial shipment costs postage. What is one parcel fee for a bulk delivery to one address becomes a multiple of that with many recipients, plus packaging and a card per shipment. The shop has to show these costs before submission, per recipient and as a total, otherwise the buyer only gets the surprise on the invoice. How shipping rules for parcels and freight are set up in a B2B shop is covered in our article on shipping costs and freight.
Collective invoice with recipient list and value per recipient
The buyer wants one invoice, not dozens. German VAT law leaves room for that. Among other things, an invoice must state the quantity and type of goods delivered (Section 14(4) sentence 1 no. 5 UStG) and the time of delivery (Section 14(4) sentence 1 no. 6 UStG). However, it can consist of several documents that together contain the required information (Section 31(1) UStDV). One of these documents must then state the consideration and the tax amount in total and identify all other documents (Section 31(1) UStDV). For the collective invoice, this means: the invoice states totals and tax and explicitly refers to the recipient list as an attachment.
The calendar month in which delivery takes place may be stated as the time of delivery (Section 31(4) UStDV). This helps when the partial shipments leave the warehouse over several days. If shipments fall across a month boundary, clarify with your tax advisor how the time of supply should be shown on the invoice.
The attachment is more than an address list. It holds one row per recipient with name, company, city, delivery note and tracking number, the items delivered and the value, split into goods value, packaging and shipping, each net and with VAT shown. Split, because the buyer has to decide for their own bookkeeping which components count toward the cost of the gift. The shop does not make that decision for them, but it provides the figures in a form that allows it.
In addition to the PDF attachment, the same list belongs in the customer portal as a downloadable CSV file with the same columns. The buyer's accounting team can process it directly instead of typing values from a PDF. If you already invoice electronically, the list goes with the e-invoice as an attachment. What XRechnung 4.0 changes for collective invoices and order references per line is described in our article on XRechnung 4.0 and collective invoices; the basics of e-invoicing in the B2B shop are on our service page.
The seller keeps invoices as a copy and the buyer as incoming invoices for eight years (Section 14b(1) UStG). If the recipient list is part of the invoice under Section 31 UStDV, it is retained with it. Where invoices and attachments live in the customer account and for how long is covered in our article on the document archive in the customer account.
Why the buyer needs the value per recipient
For the buyer, the recipient list with values is a working tool for their own taxes. Expenses for gifts to persons who are not employees of the giver may not reduce profit (Section 4(5) sentence 1 no. 1 EStG). This does not apply if the acquisition or production costs of the items given to one recipient in the financial year do not exceed 50 euros in total (Section 4(5) sentence 1 no. 1 EStG). The limit is often read as an allowance. According to the wording, it works differently: if gifts to one recipient stay at 50 euros or less in total for the year, they are deductible. If they exceed it, the deduction is lost for all gifts to that recipient, not just for the part above 50 euros.
In addition, the law requires specific records. Expenses for gifts must be recorded individually and separately from other business expenses (Section 4(7) EStG). Unless they are already excluded from deduction, they may only be taken into account when determining profit if they have been recorded in this way (Section 4(7) EStG). An invoice with a single line reading "gifts, flat rate" does little for the buyer here. An attachment with one row per recipient and a value per row is the material their accounting team can work with.
Whether the 50 euros are to be read net or gross depends on the buyer's input tax deduction. The input tax amount, to the extent it can be deducted for VAT purposes, is not part of the acquisition or production costs (Section 9b(1) EStG). For gifts that fall under the deduction ban, the input tax is not deductible either (Section 15(1a) UStG). This is another reason the attachment shows net value and VAT separately.
Some companies also pay the tax on their gifts. The law allows the income tax on non-cash gifts to business partners to be levied uniformly at a flat rate of 30 percent (Section 37b(1) EStG). The assessment basis is then the expense including VAT (Section 37b(1) EStG), non-cash benefits taxed this way are disregarded in the recipient's income (Section 37b(3) EStG), and the giver must inform the recipient that the tax has been assumed (Section 37b(3) EStG). For the shop, this leads to a small, useful feature: an optional column in the recipient list that lets the buyer add their own note to the card or an insert. Whether and how they use the flat rate is for them to decide with their tax advisor.
Anyone who chose a gift just below the limit last year should check its value again this year. Wholesale selling prices in September 2026 were 8.7 percent higher than in the same month a year earlier (Destatis). The average hides large differences: for milk, dairy products, eggs, edible oils and fats, wholesale prices in the same month were 9.7 percent below the prior-year month (Destatis). What counts, then, is the value on this year's invoice, not the memory of last year's.
The limit applies per recipient and financial year in total. If a buyer sends a gift for a company anniversary in summer and another one at year end in December, both count together. An annual overview in the customer portal that adds up the values per recipient across all bulk orders in a financial year takes this calculation off the buyer's hands. It needs two things: a stable recipient ID from the list and the start of the buyer's financial year, which is not the start of the calendar year in every company. It is fed from the invoice attachments, which are retained anyway.
No tax advice in the shop
Data protection: keep recipient data lean
The recipient list contains personal data of people who have not ordered in the shop themselves. The shop receives it from the buyer, not from the recipients themselves. For this case, Article 14 GDPR sets out what the controller must tell the data subjects, including the source the data comes from (Article 14(2)(f) GDPR). Who the controller is in your process and how the information reaches the recipients, for example through a note on the delivery note, is something to clarify with your data protection officer.
Two principles apply to the design of the list. Data must be adequate, relevant and limited to what is necessary for the purpose (Article 5(1)(c) GDPR). For delivering a gift, that means name, address and greeting, but no birthdays and no phone numbers unless the shipping provider needs them. And data may be kept in a form that identifies people only for as long as the purpose requires (Article 5(1)(e) GDPR).
In practice, this means separating two data sets. The invoice and its attachment are subject to retention, as described above. The working list in the shop, from which delivery notes and cards were produced, is deleted or anonymized once delivery is complete and returns have been resolved. For delivery notes sent out that are not accounting vouchers, the retention period ends when the invoice is sent (Section 147(3) AO). If the buyer wants to reuse their recipients next year, they deliberately save them as an address book in their customer account, with their own delete function, instead of the shop keeping every list indefinitely.
What Shopware CE includes and what is custom development
Shopware CE provides the foundations a bulk order builds on: customer accounts with an address book, validation rules per country, orders with deliveries and an administration in which delivery addresses can be changed afterwards. The ordering path with a recipient list itself is not included. The overview shows where the line runs.
| Building block | Shopware CE standard | Extension or ERP |
|---|---|---|
| Address book in the customer account | Customers manage stored addresses themselves (Shopware documentation) | Import a whole recipient list as an address book |
| Delivery address per order | One delivery to the address selected at checkout (Shopware source code) | Bulk order with list or one delivery per recipient |
| Postcode validation | Format and mandatory field configurable per country (Shopware documentation) | Apply the same rules to every row of the list |
| Change delivery address afterwards | In the administration, per order (Shopware documentation) | Buyer corrects individual recipients in the portal |
| Upload of the recipient list | Not available | Template, upload and check report per row |
| Shipping costs for many recipients | Shipping costs for the one delivery of the order | Total across all partial shipments, shown before submission |
| Collective invoice with value per recipient | Not available | Invoice attachment from ERP or shop, plus CSV export |
| Annual overview per recipient | Not available | Total per recipient and financial year in the customer portal |
The extension remains a plugin on Shopware CE and touches the checkout as little as possible. The bulk order gets its own entry point in the customer portal, while the normal cart for repeat orders stays unchanged. That keeps updates manageable and the effort predictable. What such Shopware development involves is described on our service page.
Roadmap to the first bulk order
- Review the current state: how do bulk orders arrive today, how many recipients does a typical order have, and who transfers the addresses?
- Check the ERP: does it support different ship-to parties per delivery note, or only one delivery address per order? The data model follows from that.
- Define the template: columns, mandatory fields, the character limit of the card and the items and sets released for gifts.
- Define the check rules: countries in the delivery area, postcode format, exclusion of parcel lockers for certain goods, handling of duplicates.
- Align invoice and attachment: structure of the recipient list, goods value, packaging and shipping shown separately, CSV export and e-invoice.
- Clarify data protection: informing recipients, deletion period for the working list, address book only at the buyer's request.
- Test with one customer: a real bulk order with a few recipients before the feature is opened to all business customers.
Do not schedule the rollout for the weeks in which the gifts leave the building. A feature that runs under load for the first time when the seasonal business peaks is an unnecessary risk. A start in spring or summer is better, with a pilot customer and occasions such as anniversaries or trade fairs, so that the processes are well established by year end. Free samples for many prospects are a similar case; how sample orders with limits work in the shop is covered in our article on product samples in the B2B shop.
How we implement bulk orders with many addresses
We develop bulk orders as an extension for Shopware CE: the recipient list as a template in the customer portal, the check of every row before submission, the handover to your ERP as a bulk order or as deliveries per recipient, and the return of status and tracking numbers to the portal. The collective invoice with recipient list and value per recipient is produced where your invoices are produced today, usually in the ERP, and appears as PDF and CSV in the customer account.
The extension is aimed at wholesalers and manufacturers who sell gifts, beverages, food, promotional items or packaging to business customers. What typically comes together in a B2B shop for the food trade and for packaging suppliers is described on our industry pages. Which of the three routes fits your ERP is something we clarify before a single line of code is written.
Related Articles
Ordering on Behalf of Customers: Inside Sales in B2B Shops
Since Shopware 6.6.5.0, inside sales can order in the customer account. How permissions, logging, privacy and the order channel work for phone and fax orders.
Annual Rebates in the B2B Shop: Show Tiers and Rebate Status
Annual rebates change VAT after the fact. How B2B shop and ERP handle rebate status, invoice reference and rebate document under Section 17 UStG in the account.
Selling Services and Maintenance Contracts in B2B Shops
Installation, inspection and maintenance contracts as bookable items in a B2B shop: product type without stock, pricing, service data and ERP handover.