Edge Config Integration

Overview

Edge Config provides a way to update configuration values at runtime without redeploying your application. This is powered by Vercel’s Edge Config infrastructure and allows you to control service hours, store status, and emergency messages instantly.

Edge Config values are fetched at the edge, providing ultra-low latency access to configuration worldwide.

Configuration File

Edge Config integration is implemented in src/config/edgeConfig.js:1-94.

Edge Config Keys

Three main configuration keys are supported:

service_hours

object

Controls service operating hours and availabilitySee Service Hours Configuration for details.

store_status

object

Manual store status controls (open/closed, maintenance mode)

emergency_message

object

Display emergency or important messages to customers

Configuration Structure

Service Hours

{
  "service_hours": {
    "enabled": true,
    "startHour": 8,
    "startMinute": 30,
    "endHour": 22,
    "endMinute": 50,
    "weekdaysEnabled": true,
    "weekendsEnabled": true,
    "closedDates": ["2024-01-01", "2024-12-25"],
    "timezone": "Europe/Istanbul"
  }
}

service_hours.enabled

boolean

default:"true"

Master switch for service hours

service_hours.startHour

number

default:"8"

Service start hour (24-hour format)

service_hours.startMinute

number

default:"30"

Service start minute

service_hours.endHour

number

default:"22"

Service end hour (24-hour format)

service_hours.endMinute

number

default:"50"

Service end minute

service_hours.weekdaysEnabled

boolean

default:"true"

Enable service on weekdays

service_hours.weekendsEnabled

boolean

default:"true"

Enable service on weekends

service_hours.closedDates

array

default:"[]"

Array of dates when service is closed (YYYY-MM-DD format)

service_hours.timezone

string

default:"Europe/Istanbul"

Timezone for time calculations

Store Status

{
  "store_status": {
    "isOpen": true,
    "temporarilyClosed": false,
    "maintenanceMode": false,
    "reason": ""
  }
}

store_status.isOpen

boolean

default:"true"

Master on/off switch for the entire storeSet to false to close the store completely.

store_status.temporarilyClosed

boolean

default:"false"

Temporary closure flag (e.g., for emergencies, staff shortage)

store_status.maintenanceMode

boolean

default:"false"

Maintenance mode flag (shows maintenance message to customers)

store_status.reason

string

default:""

Reason for closure (displayed to customers)Example: “Teknik bakım nedeniyle geçici olarak kapalıyız”

Emergency Message

{
  "emergency_message": {
    "enabled": false,
    "message": "",
    "priority": "normal"
  }
}

emergency_message.enabled

boolean

default:"false"

Whether to display the emergency message

emergency_message.message

string

default:""

The message text to displayExample: “Yoğun talep nedeniyle teslimat süreleri uzamıştır”

emergency_message.priority

string

default:"normal"

Message priority level: normal, warning, or urgentAffects styling and prominence of the message display.

Setup Guide

Create Edge Config Store

In your Vercel dashboard, go to Storage and create a new Edge Config store.

vercel env add EDGE_CONFIG

Get Connection String

Copy the Edge Config connection string from Vercel dashboard.It looks like: https://edge-config.vercel.com/[your-id]?token=[your-token]

Add Environment Variable

Add EDGE_CONFIG environment variable to your project:

.env.local

EDGE_CONFIG=https://edge-config.vercel.com/ecfg_xxx?token=xxx

Install Vercel Edge Config SDK

Install the required package:

npm install @vercel/edge-config

Configure Initial Values

In Vercel dashboard, add your configuration keys with initial values using the JSON structure shown above.

Usage Examples

Fetch All Settings

src/config/edgeConfig.js

import { getEdgeConfigServiceSettings } from '@/config/edgeConfig';

const settings = await getEdgeConfigServiceSettings();

console.log(settings);
// {
//   serviceHours: { startHour: 8, endHour: 22, ... },
//   storeStatus: { isOpen: true, ... },
//   emergencyMessage: { enabled: false, ... }
// }

Get Single Value

src/config/edgeConfig.js

import { getEdgeConfigValue } from '@/config/edgeConfig';

const storeStatus = await getEdgeConfigValue('store_status');

if (storeStatus.maintenanceMode) {
  console.log('Store is in maintenance mode');
}

Merge with Local Settings

src/config/edgeConfig.js

import { mergeWithEdgeConfig, DEFAULT_EDGE_CONFIG_STRUCTURE } from '@/config/edgeConfig';

const localSettings = {
  serviceHours: { startHour: 8, endHour: 20 },
  storeStatus: { isOpen: true }
};

const edgeSettings = await getEdgeConfigServiceSettings();
const merged = mergeWithEdgeConfig(localSettings, edgeSettings);

// Edge Config values override local settings
console.log(merged.serviceHours.endHour); // Uses Edge Config value

Integration with Service Hours

The service hours system automatically loads Edge Config (see src/config/serviceHours.js:39-65):

src/config/serviceHours.js

import { loadEdgeConfigSettings, isServiceOpen } from '@/config/serviceHours';

// Manually load Edge Config settings
await loadEdgeConfigSettings();

// Or let isServiceOpen() load them automatically
const open = await isServiceOpen();
// Edge Config settings are loaded and merged with defaults

API Reference

getEdgeConfigServiceSettings()

Fetches all service-related settings from Edge Config.

function getEdgeConfigServiceSettings(): Promise<{
  serviceHours: object | null,
  storeStatus: object | null,
  emergencyMessage: object | null
} | null>

Returns: Object with all settings, or null if Edge Config is unavailable Implementation (see src/config/edgeConfig.js:11-29):

Fetches all three keys in parallel using Promise.all()
Returns null and logs warning if fetch fails
Non-blocking: Application continues with default values if Edge Config fails

getEdgeConfigValue()

Fetches a single value from Edge Config.

function getEdgeConfigValue(key: string): Promise<any | null>

Parameters:

key - The Edge Config key to fetch

Returns: The value, or null if unavailable

mergeWithEdgeConfig()

Merges local settings with Edge Config values (Edge Config takes priority).

function mergeWithEdgeConfig(
  localSettings: object,
  edgeSettings: object | null
): object

Parameters:

localSettings - Default/fallback settings from code
edgeSettings - Settings from Edge Config (or null)

Returns: Merged configuration object Logic (see src/config/edgeConfig.js:68-94):

If edgeSettings is null, returns localSettings unchanged
Otherwise, spreads local settings and overwrites with Edge Config values
Handles nested objects (serviceHours, storeStatus, emergencyMessage)

Default Configuration Structure

Reference structure for Edge Config values (see src/config/edgeConfig.js:42-65):

src/config/edgeConfig.js

export const DEFAULT_EDGE_CONFIG_STRUCTURE = {
  service_hours: {
    enabled: true,
    startHour: 8,
    startMinute: 30,
    endHour: 22,
    endMinute: 50,
    weekdaysEnabled: true,
    weekendsEnabled: true,
    closedDates: [],
    timezone: "Europe/Istanbul"
  },
  store_status: {
    isOpen: true,
    temporarilyClosed: false,
    maintenanceMode: false,
    reason: ""
  },
  emergency_message: {
    enabled: false,
    message: "",
    priority: "normal"
  }
};

Common Use Cases

Emergency Store Closure

Quickly close your store without redeploying:

{
  "store_status": {
    "isOpen": false,
    "temporarilyClosed": true,
    "maintenanceMode": false,
    "reason": "Acil durum nedeniyle bugün kapalıyız. Yarın normal saatlerde açık olacağız."
  }
}

Extend Hours for Special Event

{
  "service_hours": {
    "enabled": true,
    "startHour": 8,
    "startMinute": 0,
    "endHour": 23,
    "endMinute": 59,
    "weekdaysEnabled": true,
    "weekendsEnabled": true,
    "closedDates": []
  }
}

Show Important Message

{
  "emergency_message": {
    "enabled": true,
    "message": "Ramazan Bayramı nedeniyle 10-13 Nisan arası teslimat yapılmayacaktır.",
    "priority": "warning"
  }
}

Maintenance Mode

{
  "store_status": {
    "isOpen": false,
    "temporarilyClosed": false,
    "maintenanceMode": true,
    "reason": "Sistem güncellemesi yapılıyor. 1 saat içinde tekrar açılacağız."
  }
}

Error Handling

The system is designed to be resilient:

src/config/edgeConfig.js

export const getEdgeConfigServiceSettings = async () => {
  try {
    const [serviceHours, storeStatus, emergencyMessage] = await Promise.all([...]);
    return { serviceHours, storeStatus, emergencyMessage };
  } catch (error) {
    console.warn('Edge Config yüklenemedi, varsayılan ayarlar kullanılıyor:', error);
    return null; // Application continues with defaults
  }
};

If Edge Config is unavailable, your application automatically falls back to the default configuration defined in code. This ensures your app continues working even during Edge Config outages.

Best Practices

Version Control

Keep DEFAULT_EDGE_CONFIG_STRUCTURE in your code as documentation and fallback.

Test Changes

Test Edge Config changes in staging environment before applying to production.

Monitoring

Monitor console warnings for Edge Config fetch failures.

Cache Strategy

Edge Config values are cached at the edge. Updates propagate within seconds globally.

Security Considerations

Never store sensitive data (API keys, passwords) in Edge Config. It’s designed for configuration values, not secrets.

Edge Config is read-only from your application
Only Vercel team members with appropriate permissions can modify values
Connection string should be kept in environment variables, not committed to code
Use Vercel’s environment variable management for different environments

Updating Configuration

You can update Edge Config values through:

Vercel Dashboard: Web UI for manual updates
Vercel CLI: Command-line updates
Vercel API: Programmatic updates

Using Vercel CLI

# List all items
vercel env ls

# Update a value
vercel edge-config item set store_status '{"isOpen": false, "reason": "Closed today"}'

Performance

Ultra-Low Latency

Edge Config is served from Vercel’s edge network worldwide:

Global read latency: < 10ms (P95)
Update propagation: < 10 seconds globally
Availability: 99.99% SLA

Service Hours - Controlled via Edge Config
Order Limits - Could be extended to use Edge Config
Damacana Limits - Could be extended to use Edge Config

Getting Started

Core Features

Configuration

Components

Overview

Configuration File

Edge Config Keys

Configuration Structure

Service Hours

Store Status

Emergency Message

Setup Guide

Usage Examples

Fetch All Settings

Get Single Value

Merge with Local Settings

Integration with Service Hours

API Reference

getEdgeConfigServiceSettings()

getEdgeConfigValue()

mergeWithEdgeConfig()

Default Configuration Structure

Common Use Cases

Emergency Store Closure

Extend Hours for Special Event

Show Important Message

Maintenance Mode

Error Handling

Best Practices

Version Control

Test Changes

Monitoring

Cache Strategy

Security Considerations

Updating Configuration

Using Vercel CLI

Performance

Ultra-Low Latency

Build docs developers (and LLMs) love

Getting Started

Core Features

Configuration

Components

​Overview

​Configuration File

​Edge Config Keys

​Configuration Structure

​Service Hours

​Store Status

​Emergency Message

​Setup Guide

​Usage Examples

​Fetch All Settings

​Get Single Value

​Merge with Local Settings

​Integration with Service Hours

​API Reference

​getEdgeConfigServiceSettings()

​getEdgeConfigValue()

​mergeWithEdgeConfig()

​Default Configuration Structure

​Common Use Cases

​Emergency Store Closure

​Extend Hours for Special Event

​Show Important Message

​Maintenance Mode

​Error Handling

​Best Practices

Version Control

Test Changes

Monitoring

Cache Strategy

​Security Considerations

​Updating Configuration

​Using Vercel CLI

​Performance

Ultra-Low Latency

​Related Configuration

Build docs developers (and LLMs) love

Overview

Configuration File

Edge Config Keys

Configuration Structure

Service Hours

Store Status

Emergency Message

Setup Guide

Usage Examples

Fetch All Settings

Get Single Value

Merge with Local Settings

Integration with Service Hours

API Reference

getEdgeConfigServiceSettings()

getEdgeConfigValue()

mergeWithEdgeConfig()

Default Configuration Structure

Common Use Cases

Emergency Store Closure

Extend Hours for Special Event

Show Important Message

Maintenance Mode

Error Handling

Best Practices

Security Considerations

Updating Configuration

Using Vercel CLI

Performance

Related Configuration