Customer page updates: sortable columns, custom fields, and card collection

8 min read Transactagentic commercecustomer managementpaymentsmerchant tools

Customer page updates: sortable columns, custom fields, and card collection

Managing a customer list that you cannot sort or filter by the data that matters to your business is a blunt instrument. EPD Commerce’s customer page now lets merchants sort by the columns that carry meaning, surface custom field values directly in the table, and send customers a single-use link to submit their own card details.

What changed and why it matters

The customer page serves one primary job: help a merchant find the right customer, understand their standing, and take action. Three specific gaps made that harder than it needed to be.

Sortable columns. Name, Subscriptions, Total sales, and Balance due are now all sortable. Custom field columns are sortable too, which covers the cases where a merchant has organized customers by sales rep, approval status, or territory. Phone and email are intentionally excluded: sorting a customer list alphabetically by email address is not a real workflow, and adding sort controls to columns nobody sorts adds visual noise without any benefit.

Custom fields in the table. Column management, the same mechanism already available on the Orders table, now works on the Customers table. A merchant can add columns for any custom field they have defined: a single-choice field like Sales rep, a checkbox like Credit approved, or a multi-select like Languages spoken. The values display inline and sort correctly for their field type. This closes a gap where custom data existed on the record but was invisible from the list view.

Card collection link. The “Copy link to add a card” action generates a single-use URL that the merchant can send to a customer. The customer opens it, submits their card details, and the link expires. Because each link is single-use and tied to a specific customer record, merchants need a fresh link every time, which is why it generates on demand rather than being a static address. The card collection form is the mechanism behind this flow.

How the “add customer” form was updated

Email field layout was also revised based on production data. Email addresses in the EPD Commerce customer database average 29.5 characters, and the top 20% run to 51 characters or more, with a maximum of 60. When paired with phone on a single row, the field renders at roughly 33 visible characters, which means at least one in five customers would not see their full address while typing it. A typo in an email address on a customer record is expensive to catch later, so email keeps its own full-width line.

Who benefits

Two audiences get direct value here.

Merchants running sales teams can now sort by sales rep, filter by custom approval flags, and see that data without opening individual records. A team leader can scan the full list, identify imbalances, and act on them from a single screen.

Merchants who bill subscriptions and need to collect or refresh card details on file can generate a card collection link from the customer record and send it directly. No manual card entry on the merchant side, no workaround required.

FAQ

What columns are sortable on the EPD Commerce customer page?

Name, Subscriptions, Total sales, Balance due, and any custom fields a merchant has added are all sortable. Phone and email columns are not sortable by design: those fields do not carry ordinal meaning, and sort controls on columns nobody sorts add noise to the interface without practical benefit.

How do custom fields appear in the customer table?

Merchants use column management, the same control available on the Orders table, to choose which custom fields to display. Once added, the column shows the field value for each customer and sorts correctly for that field type: alphabetically for text and single-choice fields, and by checked or unchecked state for checkboxes.

The card collection link is a single-use URL generated from a customer record. The merchant copies the link and sends it to the customer. The customer opens it and submits their card details directly. Once submitted, the link expires and cannot be reused. Merchants need a fresh link each time they want to collect or update a card on file.

No. Each link is tied to a specific customer record and is single-use. It expires after the customer submits their details. This is intentional: a reusable static link would not be traceable to a specific customer or submission event.

Where does “invite customer” appear in the interface?

The invite customer option sits on the Add customer screen, not the main customer list. The main customer page is for searching, sorting, and reviewing existing customers. Adding a new customer, whether by entering details directly or by sending an invite link, happens on a dedicated screen, which is the more logical place to choose between those two paths.


These updates are live on EPD Commerce now. Beta access is open ahead of the October public launch. Request access at epd.com or reach out to the Easy Pay Direct team to get your account set up.

Get early beta access

Request your beta invite

We respond within one business day.

Now in private beta. Powered by Easy Pay Direct.

Now in private beta

EPD Commerce brings your operations, payments, and AI-discoverable products into one connected system.

  • Chat with your data and get instant answers
  • Hands-on onboarding from our commerce team
  • Products made discoverable to AI agents by default
  • Payments, recovery, and analytics in one connected system