Seller Onboarding Guide
This guide walks sellers through setting up their account, configuring item types, and using the dashboard to manage notifications.
Getting Started
Accessing the Dashboard
- Navigate to your dashboard URL (e.g.,
https://app.notifito.com) - Click "Sign in"
- Enter your email and password
- Click "Sign in"
Dashboard Overview
After signing in, you'll see the main dashboard with:
- Header: Your tenant name and sign out button
- Navigation: Item types list
- Main Content: Your configured item types
Managing Item Types
What Are Item Types?
Item types define the products or services you sell. Each item type has:
- Name: Display name (e.g., "Sneaker", "Hotel Room")
- Slug: URL-friendly identifier (e.g., "sneaker", "room")
- Attributes: Custom fields that describe your items
- Notification Policy: How to notify subscribers
- Subscription Mode: Whether subscriptions are one-time or recurring
Creating an Item Type
- Click "New item type" button
- Fill in the basic information:
- Slug: Auto-generated or customize
- Call-to-action URL: Optional link to your product page
- Configure notification policy:
- Notify a multiple of available capacity: Limit notifications based on stock
- Set subscription mode:
- Keep notifying on each availability: Subscription stays active
- Add attributes (see below)
- Click "Save"
Editing an Item Type
- Click "Edit" next to the item type
- Modify any fields
- Click "Save"
> Note: Editing a schema creates a new version. Existing subscribers keep their original schema version.
Defining Attributes
Attributes are custom fields that describe your items. They determine:
- What information consumers provide when subscribing
- How matching works when items become available
Adding Attributes
- Click "Add attribute" in the editor
- Fill in the attribute details:
size, color)
- Label: Display name (e.g., "Size", "Color")
- Type: Data type (see below)
- Options: For enum types, list available options
- Required: Whether consumers must provide this value
- Used for matching: Whether this attribute participates in matching
- Repeat for each attribute
Attribute Types
| Type | Description | Example |
|---|---|---|
enum | Single selection from options | Size: 40, 41, 42 |
enum (multiple) | Multiple selections | Colors: red, blue |
integer | Whole number | Guests: 2 |
decimal | Decimal number | Price: 10.5 |
date | Date | Appointment: 2026-09-01 |
date_range | Date range | Stay: Sep 1-5 |
boolean | Yes/no | Gift wrap: true |
text | Free text | Notes: "Leave at door" |
Attribute Options
Required: Consumer must provide this value when subscribing Used for matching: This attribute participates in matching:- If checked: Only subscribers with matching values are notified
- If unchecked: Attribute is captured but not used for matching (e.g., "Special notes")
Example: Sneaker Store
| Key | Label | Type | Options | Required | Matchable |
|---|---|---|---|---|---|
size | Size | enum | 40, 41, 42, 43 | Yes | Yes |
color | Color | enum | red, blue, black | No | Yes |
Example: Hotel
| Key | Label | Type | Required | Matchable |
|---|---|---|---|---|
stay | Stay Dates | date_range | Yes | Yes |
guests | Number of Guests | integer | Yes | Yes |
Example: Clinic
| Key | Label | Type | Options | Required | Matchable |
|---|---|---|---|---|---|
appointment | Appointment Date | date | — | Yes | Yes |
practitioner | Practitioner | enum | Dr Ng, Dr Okafor, Any | No | Yes |
Managing Items
Items are specific instances of item types. For example:
- Item type: "Sneaker"
- Items: "Nike Air Max 90", "Nike Air Force 1"
When to Use Items
Use items when:- You have specific products with different availability
- You want to notify about specific variants
- You track inventory per item
- Availability is date-based (hotel rooms, appointments)
- All items of a type are identical
- You don't track individual inventory
Using the Notify Form
The Notify form allows you to manually signal availability from the dashboard.
Accessing the Notify Form
- Click "Notify" next to an item type
- The form loads with the item type's attributes
Sending a Notification
- Select an item (if applicable)
- Fill in attribute values (leave blank to notify all subscribers)
- Set capacity (optional)
- Click "Notify"
How It Works
The Notify form:
- Uses the same schema as the widget
- Posts to the same API endpoint as your server
- Generates a unique idempotency key (prevents duplicates)
- Shows success/error messages
Best Practices
- Leave attributes blank to notify all subscribers regardless of that attribute
- Set capacity to limit notifications based on available stock
- Use specific items when notifying about particular products
Understanding Notifications
Double Opt-in Flow
- Consumer subscribes via widget
- Confirmation email is sent automatically
- Consumer clicks confirmation link
- Subscription becomes active
- When you signal availability, matching subscribers are notified
Matching Logic
Subscribers are notified when:
- They subscribed to the same item type
- Their attribute preferences match the availability
- Their subscription is still active and not expired
Attribute Matching
| Subscription | Availability | Result |
|---|---|---|
| Size: 42 | Size: 42 | Match |
| Size: 42 | Size: 41 | No match |
| Size: (empty) | Size: 42 | Match (wildcard) |
| Size: 42 | Size: (empty) | Match (wildcard) |
Notification Policies
All: Notify all matching subscribers Capacity Multiple: Notify the oldest N subscribers, where N = capacity × factor- Example: 3 items × factor 3 = 9 subscribers notified
- Remaining subscribers stay active for next availability
Subscriber Status
| Status | Description |
|---|---|
pending_confirmation | Waiting for email confirmation |
active | Confirmed and waiting for notification |
notified | Has been notified (once mode) |
expired | Subscription expired (90 days) |
unsubscribed | Consumer unsubscribed |
Consent Ledger
Every consent action is recorded in an append-only ledger:
- Subscription granted (with IP, user agent, timestamp)
- Confirmation clicked
- Unsubscribed
This provides a complete audit trail for compliance.
API Keys
Key Types
| Key Type | Prefix | Purpose |
|---|---|---|
| Publishable | pk_ | Widget integration (safe to expose) |
| Secret | sk_ | Server-to-server API calls |
Using Keys
Widget (Publishable):<script src="https://cdn.notifito.com/notifito.js"
data-key="pk_live_your_key"
data-item-type="sneaker">
</script>
curl -X POST "https://edge.notifito.com/v1/availability" \
-H "Authorization: Bearer sk_live_your_key" \
-d '{"item_type": "sneaker", "attributes": {"size": "42"}}'
Best Practices
Schema Design
- Keep attributes minimal: Only include what you need for matching
- Use appropriate types: Don't use
textfor structured data - Mark non-matchable attributes: Free-text notes shouldn't affect matching
- Plan for changes: Schema edits create new versions; existing subscribers keep old version
Notification Strategy
- Set appropriate capacity: Don't over-notify
- Signal availability promptly: Consumers expect timely notifications
- Include all relevant attributes: More attributes = better matching
Consumer Experience
- Clear expectations: Tell consumers what they're subscribing to
- Confirmation flow: Double opt-in builds trust
- Easy unsubscribe: One-click unsubscribe in every email
- Relevant notifications: Only notify when truly available
Troubleshooting
Widget Not Working
- Check API key: Ensure you're using the publishable key
- Check item type slug: Must match exactly
- Check domain: Your domain must be registered in tenant settings
- Check browser console: Look for JavaScript errors
No Notifications Sent
- Check subscription status: Must be
active - Check attribute matching: Values must match
- Check capacity policy: May be limiting notifications
Emails Not Received
- Check spam folder: Confirmation emails may be filtered
- Check email address: Must be valid and deliverable
- Check confirmation status: Subscription must be confirmed
- Check unsubscribe status: Consumer may have unsubscribed