Seller Onboarding Guide

Version: 1.0.0

This guide walks sellers through setting up their account, configuring item types, and using the dashboard to manage notifications.

Getting Started

Accessing the Dashboard

1. Navigate to your dashboard URL (e.g., https://app.notifito.com)
2. Click "Sign in"
3. Enter your email and password
4. 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

1. Click "New item type" button
2. Fill in the basic information:
3. Name: Enter a descriptive name
4. Slug: Auto-generated or customize

5. Call-to-action URL: Optional link to your product page

6. Configure notification policy:

7. Notify everyone who matches: All matching subscribers receive notifications

8. Notify a multiple of available capacity: Limit notifications based on stock

9. Set subscription mode:

10. Notify once, then finish: Subscription ends after notification

11. Keep notifying on each availability: Subscription stays active

12. Add attributes (see below)

13. Click "Save"

Editing an Item Type

1. Click "Edit" next to the item type
2. Modify any fields
3. 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

1. Click "Add attribute" in the editor
2. Fill in the attribute details:
3. Key: Lowercase snake_case identifier (e.g., size, color)
4. Label: Display name (e.g., "Size", "Color")
5. Type: Data type (see below)
6. Options: For enum types, list available options
7. Required: Whether consumers must provide this value

8. Used for matching: Whether this attribute participates in matching

9. Repeat for each attribute

Attribute Types

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")

Allow several (enum only): Consumer can select multiple options

Example: Sneaker Store

Example: Hotel

Example: Clinic

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

Don't use items when: - Availability is date-based (hotel rooms, appointments) - All items of a type are identical - You don't track individual inventory

Creating Items

Items are created via the Push API or programmatically. The dashboard shows existing items but doesn't currently support creating them directly.

Using the Notify Form

The Notify form allows you to manually signal availability from the dashboard.

Accessing the Notify Form

1. Click "Notify" next to an item type
2. The form loads with the item type's attributes

Sending a Notification

1. Select an item (if applicable)
2. Fill in attribute values (leave blank to notify all subscribers)
3. Set capacity (optional)
4. 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

1. Consumer subscribes via widget
2. Confirmation email is sent automatically
3. Consumer clicks confirmation link
4. Subscription becomes active
5. 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 - They haven't been notified in the last 24 hours (cooldown) - Their subscription is still active and not expired

Attribute Matching

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

Managing Subscribers

Viewing Subscribers

Subscriber browsing is not available in the dashboard yet. Use the API or database queries to view subscribers.

Subscriber Status

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

Getting Your Keys

1. Your publishable key is displayed in the dashboard
2. Your secret key is provided during onboarding
3. Never share your secret key publicly

Using Keys

Widget (Publishable):

<script src="https://cdn.notifito.com/notifito.js"
        data-key="pk_live_your_key"
        data-item-type="sneaker">
</script>

Push API (Secret):

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

1. Keep attributes minimal: Only include what you need for matching
2. Use appropriate types: Don't use text for structured data
3. Mark non-matchable attributes: Free-text notes shouldn't affect matching
4. Plan for changes: Schema edits create new versions; existing subscribers keep old version

Notification Strategy

1. Set appropriate capacity: Don't over-notify
2. Use cooldowns: 24-hour cooldown prevents spam
3. Signal availability promptly: Consumers expect timely notifications
4. Include all relevant attributes: More attributes = better matching

Consumer Experience

1. Clear expectations: Tell consumers what they're subscribing to
2. Confirmation flow: Double opt-in builds trust
3. Easy unsubscribe: One-click unsubscribe in every email
4. Relevant notifications: Only notify when truly available

Troubleshooting

Widget Not Working

1. Check API key: Ensure you're using the publishable key
2. Check item type slug: Must match exactly
3. Check domain: Your domain must be registered in tenant settings
4. Check browser console: Look for JavaScript errors

No Notifications Sent

1. Check subscription status: Must be active
2. Check attribute matching: Values must match
3. Check cooldown: 24-hour cooldown between notifications
4. Check capacity policy: May be limiting notifications

Emails Not Received

1. Check spam folder: Confirmation emails may be filtered
2. Check email address: Must be valid and deliverable
3. Check confirmation status: Subscription must be confirmed
4. Check unsubscribe status: Consumer may have unsubscribed

Related Documentation

• Widget Integration — Embed the widget
• Edge API Reference — Push availability via API
• Attribute Types — The seven data types