# For e-commerce

> Markdown version of https://postlake.dev/use-cases/e-commerce . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

Your catalogue already knows what launched. Your social accounts should not need telling separately.

## The problem

Product launches, restocks and price drops are already events in your system. Announcing them is a manual job somebody does later, or forgets, and the networks that matter most are the ones with the fussiest media rules.

## What PostLake does about it

### Publish from the event

A restock fires a webhook in your system; that becomes a post. No one retypes anything.

### The visual networks, properly

Pinterest and Instagram carry the most commercial intent and the strictest media rules. Both are checked against their real pixel bounds and formats before anything is sent.

### Schedule a drop

Queue the announcement for the exact local moment the drop opens, in the timezone you actually mean, through a clock change.

### See what sold

Clicks and saves come back alongside impressions, so the post that moved stock is identifiable rather than assumed.

## How it fits together

Trigger on your own events, upload the product image once, post to every channel with one call.

## Common questions

**Can I post products automatically when they go live?**

Yes. Trigger on whatever event your system already emits and publish from it. Nothing needs re-entering by hand.

**Which networks matter most for e-commerce?**

Pinterest and Instagram carry the strongest commercial intent, and both have strict media rules. Those rules are enforced up front, so a launch post does not fail at the moment it matters.

**Can I schedule a drop for an exact time?**

Yes, in a named timezone rather than UTC, so it fires at the local moment you meant even across a clock change.