Why should you care?

ShopNest enterprise rollout needs audit columns, row versioning, and tenant isolation designed upfront — retrofitting costs months.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

public abstract class AuditableEntity
{
    public DateTime CreatedAt { get; set; }
    public string CreatedBy { get; set; } = "";
    public DateTime? UpdatedAt { get; set; }
    public string? UpdatedBy { get; set; }
    public byte[] RowVersion { get; set; } = Array.Empty<byte>();
}

public class Product : AuditableEntity
{
    public int Id { get; set; }
    public string Name { get; set; } = "";
}

// Fluent:
modelBuilder.Entity<Product>().Property(p => p.RowVersion).IsRowVersion();

What happened?

• AuditableEntity base adds enterprise audit fields.
• IsRowVersion maps SQL rowversion for optimistic concurrency across ShopNest admin editors.

Practice next

1. Define base entities for audit, soft delete, tenant key.
2. Document naming conventions and schema (dbo vs catalog).
3. Plan index strategy with DBA before first production migration.
4. Add ISaveChangesInterceptor to fill CreatedAt/CreatedBy automatically.
5. Introduce TenantId on all entities with global query filter.

Remember

Enterprise schema plans audit and concurrency. Base classes reduce repeated Fluent config. Align EF model with DBA standards early.

ShopNest enterprise baseline

Architecture board approves AuditableEntity and RowVersion on all mutable catalog tables.

Outcome: Audit trail and concurrency ready before multi-team contribution.