Updated 28 October 2026
A bulletin is read in the pew, taken home, stuck on a fridge and printed again next Sunday with most of it unchanged. A code on it can carry what won’t fit on the page: the full notices, last week’s sermon, a sign-up form, a way to give. Set the codes up well once and the template can stay as it is for years.
One code that stays in the template
The simplest set-up is a code that never changes, opening a page that does. Make a This week page on your church’s website, update it before Sunday, and print the same code in every bulletin. This works on the Free plan, where a code always opens the link it was made with: the link stays the same, and the page behind it is new each week.
If the notices live somewhere new each week, such as a fresh post or document, the code itself has to move. On Plus or Pro you change where it goes from the code’s page, and everyone who scans sees the new page within a minute. On Plus, each code can change where it goes up to 10 times a month; on Pro, as often as you like. A weekly change uses four or five of those ten. Plus suits a one-off event or a programme that must keep working for years, such as a weekly bulletin, and if the church ever stops paying, the code goes on opening the last page it was given.
A separate code for giving
Give giving its own code, labelled “Scan to give”, rather than burying it on the notices page. Point it at the giving page or payment link your church already has: the page with your bank details for EFT, say, or a SnapScan or Zapper link set up for offerings. Baobab QR never takes or touches the money; the code only opens that link. Before you print, open the link on a phone that doesn’t have the payment app, to see what a visitor will see.
Put the giving code near the offering box and on the back page of the bulletin, in the same place every week, so regulars know where to find it.
Sign-ups, services and visitors
The Free plan saves 3 codes in your account, which suits a small church: one for the notices, one for giving and one for a sign-up form, such as small groups or the tea rota. Plus holds 10 codes and Pro 100, for a church with many ministries. Some codes cost nothing and don’t count towards any plan:
- An Event tool code adds one service or meeting to a phone’s calendar, with the date, time and place: the carol service, a baptism Sunday, the annual general meeting. It’s made in your browser and you can make as many as you like, but it can’t change once printed, and it holds a single day, so link to the camp’s page for a weekend away.
- A Wi-Fi code on the hall’s wall lets visitors join the guest network without asking for the password.
We don’t host sermon recordings: put them on your website or a video site, and link the code to the page listing them all, not to this week’s recording.
How big to print it
The line under your code says how big to print it: at least 2 cm wide for every 20 cm of scanning distance.
| Where | Scanning distance | Code at least |
|---|---|---|
| The bulletin, read in the pew | About 30 cm | 3 cm |
| A card on the welcome desk | About 50 cm | 5 cm |
| The noticeboard in the foyer | About 1 metre | 10 cm |
| The projector screen, from the back row | About 10 metres | 1 metre on the screen |
The last row is why a code on the screen rarely reaches everyone: from the back it has to fill much of the screen. Leave it up for a minute or two, and keep the same code in the bulletin for those further back.
An event code holds the whole service in its pattern, so the Event tool’s line asks for more, about 3 cm for every 20 cm: a carol-service code in the bulletin needs about 4.5 cm. Keep its place and details short and it stays smaller.
Photocopies and print runs
Many bulletins are photocopied, and copiers darken, lighten and blur. Keep the code black or a very dark colour on white paper, and test a photocopied bulletin, not the original. If you shrink the template from A4 to A5, check that the code is still at least 3 cm wide. With a frame, measure the code inside it.
Before Sunday:
- Download the code first. Until you do, the preview opens a page on our site saying the code isn’t working yet.
- Scan a copy from the actual print run with two phones, in the church’s own light.
- Open the notices page and the giving link on mobile data.
Keep it trustworthy
A giving code is the one most worth protecting. Someone could stick their own code over the one in the foyer, and no QR service can prevent that by itself. Print codes into the bulletin and the noticeboard rather than on stickers, print the giving code’s short address beside it (for example baobabqr.app/7K2XQ9P) so people can check it matches what their camera shows, and glance over the foyer’s notices each Sunday.
We check every link before your code goes live, again the next day, and every month. When you change where a code goes, we check the new link first. Anyone can report a code. We don’t store IP addresses or use cookies when someone scans a code.
See what’s read
Every plan shows each code’s total scans, a rough count of how many people open the notices. On Plus (the last 30 days) and Pro (the full history), a code’s page adds scans by day and, once it has 10 scans in the period, its busiest hours and weekdays: you’ll see whether people read the notices during the service or later in the week. If you’d rather not record that much, set the code’s Tracking to count only, or off.
Mistakes to avoid
- A Free code in the template that opens one week’s notices document.
- Giving and notices squeezed onto one code.
- A code shrunk or faded by the photocopier.
- A sermon code that opens a single recording, printed into the template.