If visits were missed because of a system outage, a scanner issue, or check-ins tracked on paper, you donât have to add them one at a time. The Mass Update / Import Tool lets you upload a CSV file and create many check-ins at once, then preview the results before anything is saved.
This guide walks through the full process: opening the tool, preparing your file, previewing your import, and confirming the results.
BEFORE YOU BEGINYouâll need the BranchID and MemberID values for every check-in you plan to add, plus access to the Junk Drawer area of Daxko Core. If you donât see the Junk Drawer option in your profile menu, contact your system administrator to have it enabled. For your first import, start with a small batch of five to ten rows. |
Open the Junk Drawer
Select your user profile in the upper-right corner of the screen, then choose Junk Drawer from the dropdown menu.
Open the Mass Update / Import Tool
On the Junk Drawer page, select Mass update / import tool.
Choose the Add Branch Check Ins update type
Open the Select Update Type dropdown and choose Add Branch Check Ins.
Choosing the update type first is important; it tells the tool how to read your file and displays the matching CSV requirements on screen.
Prepare your CSV file
Build a spreadsheet with one row for each check-in you want to create, then save it as a .csv file. Use these exact column names in the first row:
Column name | Requirement | What it does |
BranchID | Required | Identifies the branch where the check-in is recorded. |
MemberID | Required | Identifies the member the check-in belongs to. |
Created | Optional | Sets the date and time of the check-in, including backdated visits. If left out, the tool applies its default. |
Example File Contents
BranchID | MemberID | Created |
1 | 100245 | 2026-09-08 06:15:00 |
1 | 100311 | 2026-09-08 17:42:00 |
2 | 100480 | 2026-09-09 12:05:00 |
DATE AND TIME FORMATThe Created column must use the format YYYY-MM-DD HH:MM:SS. For example, 2026-09-10 09:30:00. Use the 24-hour clock, and include all six values (year, month, day, hour, minute, second). If your spreadsheet reformats the dates automatically, set the column to plain text before saving. |
Tips for a clean file
Spell the column headers exactly as shown, including capitalization.
Leave out any columns the tool doesnât list - extra columns can cause the import to fail.
Remove blank rows at the bottom of the file before saving.
Double-check IDs against a report or export rather than typing them from memory. An incorrect MemberID will assign the visit to the wrong member.
Save your source spreadsheet. If you need to correct or re-run the import, youâll want the original.
Upload File and Preview
Confirm that Add Branch Check Ins is still selected under Select Update Type. Then, under Choose CSV File to Upload, select Choose File and pick the CSV you just saved.
Leave Simulate Results (View Preview before final submit) selected, then choose Preview Process. The tool will check your file without saving changes, allowing you to fix any issues before submitting.
Review and Submit
Compare the preview results against the check-ins you intended to create. Before you complete the final submission, confirm the following:
Branch: Each visit is landing at the correct location.
Member: The members listed are the ones you meant to credit.
Date and Time: Any Created values match the actual visit times, and backdated entries fall on the days you expect.
Row Count: The number of check-ins in the preview matches the number of rows in your file.
Resolve any issues the preview reports before completing the final submission. If something looks wrong, correct your CSV and run the preview again. NOTE: Thereâs no limit on how many times you can preview a file.
IMPORT CAREFULLYCheck-ins created by this tool are recorded as real member visits and may feed into attendance reporting and usage metrics. Because bulk imports are difficult to undo, treat the preview as your safety check. |
Troubleshooting
Issue: The Junk Drawer option isnât in my profile menu.
Resolution: This area is permission-based. Contact your organizationâs Daxko Core administrator to request access.
Issue: My file wonât upload or the preview returns errors.
Resolution: Work through these in order:
Confirm the file is saved as .csv, not .xlsx.
Check the header row for typos, extra spaces, or renamed columns.
Verify every Created value uses YYYY-MM-DD HH:MM:SS. This is the most common cause of failed check-in imports.
Remove any columns that arenât listed in the on-screen requirements.
Delete trailing blank rows.
Issue: The check-ins appear on the wrong date.
Solution: The Created column controls the visit date and time. If itâs missing or mis formatted, the check-in wonât land where you expect. Review the Created values in your source file and re-run the preview.
Issue: I imported check-ins by mistake.
Solution: Contact Daxko Core Support with the details of the import: the branch, the members affected, the date range, and the file you uploaded. Having your original CSV on hand will speed up the correction.
Still need help? Reach out to the Daxko Core Customer Support Team in the Bubble.