Using date format tokens for Concierge messaging
When customizing Concierge omessaging in Recharge, you can use date format tokens to display dynamic dates in a format that works for your customers. Tokens are short codes that Recharge replaces with the actual date values when a message is sent.
This guide covers the date format tokens available when customizing message content in Recharge.
- Shopify Checkout Integration
- Migrated Shopify Checkout Integration
How it works
Date format tokens are placeholders you include in a message template's date format field. When a message is triggered, Recharge evaluates the customer's date and substitutes each token with its corresponding value. Tokens are case-sensitive so MMMM outputs a full month name like "January," while MM outputs the zero-padded number "01." You can combine multiple tokens, separators, and literal text to build the exact format you need.
For example, the format string MMMM D, YYYY would produce a date like January 5, 2025.
Available tokens
The following tokens are supported for date formatting:
| Category | Token | Output example |
|---|---|---|
| Year | YYYY |
2024, 2025 |
YY |
24, 25 | |
| Month | MMMM |
January, February, March |
MMM |
Jan, Feb, Mar | |
MM |
01, 02, 03 ... 11, 12 | |
M |
1, 2, 3 ... 11, 12 | |
Mo |
1st, 2nd, 3rd ... 12th | |
| Day of month | DD |
01, 02, 03 ... 30, 31 |
D |
1, 2, 3 ... 30, 31 | |
Do |
1st, 2nd, 3rd ... 30th, 31st | |
| Day of week | dddd |
Monday, Tuesday, Wednesday |
ddd |
Mon, Tue, Wed | |
dd |
Mo, Tu, We | |
| Quarter | Q |
1, 2, 3, 4 |
Qo |
1st, 2nd, 3rd, 4th | |
| Hour | HH |
00, 01 ... 22, 23 (24-hour) |
H |
0, 1 ... 22, 23 (24-hour) | |
hh |
01, 02 ... 11, 12 (12-hour) | |
h |
1, 2 ... 11, 12 (12-hour) | |
| AM / PM | A |
AM, PM |
| Minute | mm |
00, 01 ... 58, 59 |
m |
0, 1 ... 58, 59 | |
| Second | ss |
00, 01 ... 58, 59 |
s |
0, 1 ... 58, 59 |
MM (uppercase) is the month, while mm (lowercase) is the minute. Using the wrong case will produce unexpected output.Common date patterns
The following patterns cover the formats merchants most commonly use in customer-facing messages. All examples use the date January 5, 2025.
| Format string | Output | When to use |
|---|---|---|
MMMM D, YYYY |
January 5, 2025 | Full written-out date; friendly and unambiguous for all regions |
MMM D, YYYY |
Jan 5, 2025 | Compact but still readable; good for short notifications |
MM/DD/YYYY |
01/05/2025 | US-style numeric format |
DD/MM/YYYY |
05/01/2025 | UK/EU-style numeric format |
YYYY-MM-DD |
2025-01-05 | ISO 8601 format; useful for system-style or B2B messaging |
dddd, MMMM Do, YYYY |
Sunday, January 5th, 2025 | Full date with day name and ordinal; most explicit option |
ddd, MMM D |
Sun, Jan 5 | Short date without year; useful when the year is implied |
MMMM Do |
January 5th | Month and ordinal day only; for recurring events where the year isn't needed |
M/D/YY |
1/5/25 | Very compact; use only when space is limited and audience is US-based |
