Skip to main content

Member upload

The member upload screen allows you to update member information, add new members, and/or delete existing ones.

Upload

You can batch upload member information in a CSV file using the corresponding member ID as the key. Entries with no member ID will be treated as new registrations.

Note: You can delete a member by setting the corresponding delete flag value to 1.

Image from Gyazo

FieldDescription
File settingsSelect a CSV file from your local drive to upload.
CharsetCharacter encoding of the uploaded CSV file.
No value behaviorConfigure actions for missing values.
  • Password settings: Checking the "Randomly generated" box sets a random password for any newly added members.
  • Search from 'E-mail' when 'Member ID' is not available.: Enabling this option sets the e-mail address as the key instead of the member ID.
    (Note: Entries with invalid e-mail addresses will not be registered.)
  • Search from 'Login ID' when 'Member ID' is not available.: Enabling this option sets the login ID as the key instead of the member ID.
    (Note: Entries with invalid login IDs will not be registered.)
Registered groupsSpecify the user group(s) for the uploaded member list. If no options are specified in the CSV or the dropdown list below, new members will be assigned based on the default group settings, and existing members will retain their current group settings.

Actions

ButtonDescription
UploadUpdate member information using the uploaded CSV file.
Upload using batch processBatch process the upload. Use this option if the uploaded file contains a large number of items.

Overwriting points (ec_point column)

The ec_point column of the CSV overwrites the member's point balance. When the balance changes, the difference is recorded in the point history (reason = "CSVで更新"). The bulk_upsert API behaves the same way.

CSV contentBalancePoint history
ec_point column present with a value larger than the current balanceOverwrittenDifference recorded as a grant
ec_point column present with a value smaller than the current balanceOverwrittenDifference recorded as spending
ec_point column present with the same value as the current balanceNo changeNot recorded
ec_point column present but empty + empty-update setting ONCleared (empty)The full previous balance recorded as spending
New member row with ec_pointSet as the initial valueInitial balance recorded as a grant
No ec_point columnNo change at allNot recorded
note

If recording the point history fails for a row after the balance has been overwritten, the error "会員データは更新されましたが、ポイント履歴の記録に失敗しました。" (Member data was updated, but recording the point history failed.) is displayed. In this case, the member data of that row (including the balance overwrite) itself has been updated.

note

For the point specifications (balance, history, expiration) and API operations, see E-commerce point specifications and point update/history APIs.


Support

If you have any other questions, please contact us or check out Our Slack Community.