Replication design issue.

Hi, I need opinion for my system that I consider replication.
Our company has about 300 stores and each store has Sql-Server DB, called TimeDB.
Each store TimeDB contains their own data only.
And main office has Sql-server DB called TimeDBHQ which contains all stores' data that are posted from all the stores.
Most of time, store post their data to TimeDBHQ in daily base by application. And TimeDBHQ distribute policy data and modified data to stores corresponding the data.

All data transfer are handled by application.
But, I consider Replication for the periodical transfer and consider application as preserved way.

The issue I considered first time when I designed the system without using replication is that there are too many subscriber/distributros.
I use replication for several servers, about 3-5, which is very small number comparing to 300 or more.

Here is my question,
Is it good that I use replication for my system?
because replication made by MS is more stable and bug free than my application.
and My first hasitation is on whether replication works stable among more than 300 servers..

If anyone has experiance with this issue please post any idea,
It will be big help!!!

thank you..What compamy?

Even at 10k a licence, that's huge...

You sure we're talking sql server?|||we use sql server personal editon on store side.
anyway..
please consern the issue of the design.