Export Limitation Solar Design: Zero-Export C&I

Last updated: November 2026

SurgePV publishes this post and sells solar design software.

For a growing number of commercial sites, the design question is no longer how much PV the roof can hold. It is how much PV the meter will let onto the grid. Export limitation has moved from a niche workaround to a core engineering deliverable on commercial and industrial projects, because network operators cap or ban export where the local grid is constrained or export earns little.

This guide covers the engineering workflow for export-limited and zero-export commercial PV: control architecture, hardware, sizing under a cap, battery recovery, communication, multi-inverter control and commissioning tests. Numbers in worked examples are assumptions for illustration. Limits, timings and test criteria for a real site come from the grid code and the connection offer.

In this guide:

• The three export limitation modes (static, dynamic and absolute zero) and when each applies
• Why network operators impose export caps on commercial connections
• Which documents set export limit rules in each market
• Hardware architecture: meters, current transformers, gateways and inverter requirements
• The 8-step zero-export design workflow, from load profile to commissioning
• A one-day sizing illustration with assumed numbers
• Battery sizing for curtailment recovery
• Communication protocols and response-time checks
• Multi-inverter and multi-injection-point control
• Commissioning and acceptance tests
• Eight common design mistakes

What Export Limitation Means and the Three Modes

Export limitation is a continuous control loop that measures power flow at the point of common coupling (PCC) and adjusts inverter output to keep grid feed-in below a configured setpoint. The setpoint is not always zero. It can be a share of inverter nameplate, a fixed kW value, or a strict zero with a small tolerance.

Three modes cover almost every commercial deployment. For the plain-language definition, see the grid export limitation glossary entry.

Static Export Limit

The simplest mode. The inverter is configured with a fixed kW cap it will never exceed, regardless of on-site load. A 500 kW PV system with a 200 kW static export limit can output up to 200 kW to the grid plus whatever the on-site load consumes. The cap is a constant, not a dynamic value.

Static limits suit sites where the operator wants a guaranteed maximum injection regardless of behind-the-meter activity. They are easy to commission: set a value and lock it. They use the least of the available headroom, because they do not respond to the on-site load.

Dynamic Export Limit

The setpoint is fixed, but the actual injection adjusts in real time with on-site consumption. If the site draws 150 kW and the array could produce 400 kW, the inverters hold output at 150 kW plus the export setpoint. As the load changes through the day, the output follows it.

Dynamic limits use the full headroom under the cap. They need a CT or meter at the service entrance and a fast control loop. Many modern string and central inverters offer this mode, but support differs by model and firmware, so check the datasheet and the manufacturer’s documentation for the exact inverter. Use the generation and financial tool to model how much generation clears the cap under a dynamic limit.

Zero Export

The absolute case. The setpoint is zero or a small dead-band. The inverter never exports surplus, and any on-site under-consumption causes immediate curtailment. Some network operators issue zero-export connection offers, and some markets require it for certain connection types. Read the exact wording, because “no export” can mean different things.

Zero export is the strictest design constraint because the optimization target changes. Without storage, useful generation is capped by the daytime load floor, the lowest demand during the solar window. A large gap between array size and load floor means a large share of peak output is curtailed. For device-level detail, see the zero export device guide.

Why Network Operators Impose Export Caps on Commercial Connections

Export limits exist because many local low-voltage and medium-voltage networks were not designed for reverse power flow at today’s PV penetration. Five constraints drive the cap.

Transformer Backfeed

Distribution transformers are usually sized for power flowing from the substation toward the load. When PV exports exceed local demand, current reverses through the transformer. The operator may cap export so that reverse flow stays within the transformer’s rating and the loading it was designed for.

Voltage Rise

Pushing power through a cable raises voltage at the injection point. Standards such as EN 50160 set limits on supply voltage variation, and network operators often set tighter operational limits. On a long feeder, a large PV system can lift voltage above the allowed band at the inverter terminals, tripping the system or breaching the grid code. Export limitation keeps voltage in band by capping injection.

Protection Coordination

Distribution protection schemes are often designed around current flowing from the substation toward a fault. Reverse current from PV can mask faults, delay protection operation or interfere with directional relays. Above a certain penetration, the operator either upgrades the protection scheme or limits export, and limiting is usually cheaper.

Capacity Allocation

Many network operators allocate feeder capacity first come, first served. When a feeder is at capacity, new connections can come with export caps to avoid further loading. This is a common reason for caps on dense urban commercial connections.

Tariff Structure

In markets without net metering, or with strict net billing, export may earn nothing or earn a price below avoided cost. The owner has little reason to export and the operator little reason to accept it. A zero export configuration can then be the simplest outcome for both parties.

The five drivers stack. A single project can face transformer limits, voltage rise and protection coordination at once, and the operator may issue a zero export offer instead of running separate studies.

Where Export Limit Rules Are Written

Export limitation rules sit in national grid codes, interconnection standards and network operator connection conditions. The table lists documents to start from. It does not list limits, because limits change and depend on the operator and connection size. Obtain the current text and the operator’s connection offer for the site.

The detailed national rules are covered in the grid export limitation rules by country post. For UK schemes, the ENA EREC G100 Issue 2 Amendment 2 publication is titled Technical Requirements Customer Export and Import Limitation Schemes. The IEEE 1547-2018 standard sets interconnection and interoperability requirements for distributed energy resources in the US.

Hardware Architecture for Export-Limited Commercial PV

A commercial export limitation system has four hardware blocks. Get any one wrong and the control loop runs too slowly, runs out of headroom, or misreads the meter and trips the system.

Block 1: Meter or Current Transformers at the Point of Common Coupling

The system needs real-time grid power flow with directional awareness. There are two options.

Bi-directional meter. A three-phase meter installed at the service entrance, downstream of the utility meter, that reports power flow over Modbus RTU or TCP. Check the accuracy class against the tolerance in the connection offer.

Current transformers plus a power analyzer. Three split-core or solid-core CTs around the incoming phases, wired to a power analyzer or directly to the inverter’s CT input. This is often cheaper, and a direct CT input usually responds faster than a meter polled over Modbus.

Match CT and meter accuracy to the export tolerance. A tight tolerance needs better accuracy classes than a loose one.

Block 2: Zero Export Controller or Gateway

The controller reads meter or CT values, compares them with the setpoint, and issues power limit commands to the inverters. There are three options.

Inverter-native control. Many string inverters accept CT inputs directly and run the export control loop in firmware. No external gateway is needed for single-inverter sites or homogeneous clusters, if the datasheet confirms the feature for the exact model.

Vendor gateway. Inverter manufacturers offer data loggers and gateways that handle cluster-level control and meter aggregation. Use them when the site has several inverters from one manufacturer.

Vendor-agnostic gateway. A third-party controller or a PLC running the control logic. It is useful when the site mixes inverter brands or must integrate with SCADA, and it works with any inverter that exposes a power limit register. Expect more commissioning effort than with a single-vendor cluster.

Block 3: Communication Backbone

Three approaches are common.

Modbus RTU over RS-485. Daisy-chain wiring with up to 32 unit loads per segment without a repeater. Most commercial inverters expose power limit registers over Modbus RTU. Latency depends on baud rate, cable length and node count.

Modbus TCP over Ethernet. Star topology through a switch, with more nodes possible and generally lower latency. Use it for sites with structured cabling or large clusters. Keep PV control traffic on a dedicated VLAN or behind an industrial firewall, separate from corporate IT.

SunSpec Modbus. A standard register map maintained by the SunSpec Alliance. According to the SunSpec Alliance, its Modbus specification covers shared settings for monitoring and controlling distributed energy resources, including export limits. Verify support for the exact inverter model and firmware before you specify a multi-vendor cluster.

Block 4: Inverter with External Power Limit Support

Not every inverter accepts external power limit commands. Look for these capabilities in the datasheet:

• Power limit register. A Modbus holding register that, when written, reduces the inverter’s AC output to the commanded value.
• Setpoint timeout. The inverter should trip or fall back to a safe state if the setpoint is not refreshed within a configured window. The required window comes from the grid code or connection offer.
• Ramp rate control. Optional, but it affects how quickly output follows the command and how much flicker the site produces.

Older inverters without external power limit support cannot be retrofitted into a zero export system without an upstream curtailment device, usually a contactor on the AC side. That is a poor solution because it loses all PV output during the disconnect, not just the surplus.

For new commercial designs, record the inverter model, firmware and control interface in the design package. SurgePV’s published scope includes electrical workflow support and bill-of-materials output. Whether a given solar design platform holds inverter control data for your equipment is something to check in a demo.

The 8-Step Zero Export Design Workflow

A clean zero export design moves through eight steps. Skipping one tends to show up later as a commissioning failure or a curtailment surprise.

Step 1: Load Profile Analysis

Pull at least 12 months of 15-minute or 30-minute interval data from the site’s meter. The data drives every sizing decision. Three statistics matter most.

• Daytime load floor. A low percentile, such as the 5th, of demand during the solar window. It is the practical upper bound of useful PV without storage under a zero export limit.
• Daytime average load. The mean demand during the solar window.
• Weekend versus weekday difference. Many commercial sites drop to a small baseline on weekends, so a large Monday load can become a small Sunday load.

Plot the data as a heat map with hour of day on one axis and day of year on the other. Seasonal patterns and weekend dips show at a glance.

Step 2: Irradiance and Generation Profile

Use a typical meteorological year or a satellite-derived hourly dataset for the site coordinates. Convert it to expected hourly generation for a draft system size, using module rating, tilt, azimuth and losses. Match the generation profile against the load profile from Step 1.

The overlap is useful generation. Generation above the load is curtailment. Load above generation is grid import.

Step 3: Set the Curtailment Tolerance

Decide how much curtailment the project can absorb. The reference points below are rules of thumb, not standards.

• Low curtailment. The load follows irradiance closely, the array is sized under the load floor, or storage is large.
• Moderate curtailment. A well-designed system without storage on a daytime-active site.
• High curtailment. The array is oversized, the load is weekend-idle, or storage is needed to make the economics work.

Run the generation and financial tool with the load and irradiance data to find the system size that meets the target.

Step 4: Select the Control Architecture

Choose between inverter-native control, a vendor gateway and a vendor-agnostic gateway. Three questions decide it.

• How many inverters? Single-inverter sites can use native control. Multi-inverter sites usually need a gateway.
• Single brand or mixed? Mixed brands point to a vendor-agnostic gateway.
• SCADA integration? Sites with plant SCADA need a controller that supports the plant’s protocol.

Step 5: Specify the Meter and CTs

Match meter and CT accuracy to the tolerance in the connection offer. A tight dead-band needs better accuracy classes than a loose one.

Place the meter on the utility side of any source that should not count toward consumption. A common error is placing the CT on the wrong side of a backup generator transfer switch, which counts generator output as load during testing.

Step 6: Tune the Control Loop

Three parameters need sign-off before commissioning.

• Setpoint. The export cap in kW. Usually zero for zero export. Some grid codes allow a small positive value to absorb measurement noise, so check the connection offer.
• Dead-band. The window around the setpoint in which the controller does not act. A 1 kW dead-band around a 0 kW setpoint means the controller acts on +1 kW export but not on +0.5 kW.
• Response time. The time from a detected violation to throttled output. Set it to the fastest the protocol supports, and verify it against the connection offer.

Step 7: Battery Storage Sizing (If Applicable)

If curtailment exceeds the tolerance from Step 3, consider storage. Size the battery to capture the curtailed kWh on a typical clear day, not the worst case, because sizing for the rarest sunny weekend leaves much of the battery idle most of the year.

A starting rule of thumb is a battery capacity of 0.6 to 0.8 times the daily curtailed kWh. Take round-trip efficiency from the battery datasheet, since recovered energy is lower than stored energy.

Step 8: Commissioning and Acceptance Test

The last design step is the commissioning plan. Document the test sequence, expected response times, pass thresholds and the rollback procedure if a test fails. The full protocol is covered later in this guide.

Sizing Under an Export Cap: A One-Day Illustration

This example uses assumed numbers to show the logic. It is not a site result or an annual simulation. Assume a commercial plant with a weekday load of 145 kW before 08:00 and after 17:00 and 280 kW from 08:00 to 17:00, and a weekend load of 60 kW. Assume a clear day, a sine-shaped PV output between 06:00 and 18:00, and an output of 85% of DC array size at the daily peak. The site has a zero export limit.

The weekday numbers show why the load floor matters. Arrays whose peak output stays under the daytime load lose nothing on this day, and the loss starts once the peak passes the load. The weekend row shows the larger risk: with a 60 kW load, every array size curtails at least half of its output. A real design must be checked against the whole load profile, including weekends and holidays.

With a Battery

Storage helps most on the weekday surplus. The table assumes the battery absorbs curtailed energy up to its capacity before round-trip losses, which a real design must include.

A 300 kWh or 500 kWh battery cuts the weekday loss but barely dents the weekend surplus. That is why a site with idle weekends may need a smaller array, export permission or a load that runs on weekends, not just more storage.

Battery Sizing for Curtailment Recovery

Battery sizing for export-limited systems differs from sizing for time-of-use arbitrage or backup. The goal is to capture surplus PV during the curtailment window and discharge it during the import window. Three methods are common. For wider battery sizing, see the commercial battery storage sizing guide.

Method 1: Daily Curtailment Average

Take the average daily curtailment in kWh from the simulation and multiply by a factor such as 0.7. The result is a battery size that captures most curtailment without paying for capacity that is rarely used.

Method 2: 90th Percentile

Size to the 90th percentile of daily curtailment, not the maximum. The maximum usually occurs on a few sunny, low-load days. Sizing to the 90th percentile keeps utilization higher.

Method 3: Self-Consumption Target

Set a target self-consumption ratio and work back to the battery size. This suits projects where the constraint is a contractual self-consumption percentage and not a curtailment percentage.

For all three methods, check the battery’s charge power as well as its energy. A morning ramp can deliver surplus faster than a small-power battery can absorb, so the system curtails through the ramp even when the battery has room.

Communication Protocols and Response-Time Checks

The control loop has four legs: meter to controller, controller to inverter, inverter ramp, and feedback to the meter. Total loop latency is the sum of all four, and each protocol adds its own delay.

Modbus RTU (RS-485)

The typical commercial deployment uses multidrop wiring with a limited number of nodes per segment. Latency depends on baud rate, cable length, node count and polling cycle. Tune it by raising the baud rate if the cable length allows, shortening the polling cycle and setting the inverter ramp rate as fast as the grid code allows.

Modbus TCP (Ethernet)

Ethernet generally gives lower latency and more nodes, at higher cost. Use it for large clusters, sites already wired with Ethernet, or sites where SCADA is TCP-native.

Hardwired Analog

An analog signal from the meter to the inverter can respond quickly because it skips polling. The drawback is wiring one loop per inverter unless you add multiplexing, so it suits single-inverter sites with strict response requirements.

Setpoint Timeout

Every grid code or connection offer that requires an external setpoint also says what the inverter must do if that setpoint is lost. Configure the timeout and the fallback state, trip or curtail to zero, to match the document. Do not copy a timeout from another site or country.

Measure the Loop

Do not rely on datasheet latencies. During commissioning, create a load step and record the time from the step to the throttled output, then compare it with the requirement in the connection offer.

Multi-Inverter and Multi-Injection-Point Control

Single-inverter sites are simple. Multi-inverter and multi-injection-point sites need care over how the limit command is divided.

Single-Point Injection, Multi-Inverter

The site has one PCC and several inverters on the same bus. The controller reads grid power at the PCC and divides the limit command across the inverters. There are two common strategies.

Equal share. The controller sends the same limit to every inverter. It is simple, but when one inverter faults the others do not pick up the slack. Use it only on identical, redundant clusters.

Proportional share. The controller monitors each inverter’s output and divides the limit in proportion to current production. It behaves better under partial faults, because the remaining inverters can ramp up to fill the gap up to the cap.

Multi-Point Injection

The site has several PCCs, for example a campus with separate buildings and separate utility connections. Each PCC has its own meter and its own limit, and the controller must enforce each independently. There are two architectures.

Federated. Each PCC has its own controller and meter, and the local controller manages the inverters on that bus.

Centralized. One controller polls all PCC meters and commands all inverters. It is more flexible, and surplus from a low-load building can serve a high-load building if the electrical topology allows, but it needs a stronger controller and a wider communication backbone.

Most multi-PCC sites use federated control, because separate utility connections rarely allow surplus to move between buses.

Generator and Storage on the Same Site

Sites with backup generators or batteries need extra logic. The controller has to separate PV export, battery export and generator export. Wire the meter to read net power flow at the utility boundary and let the controller compute the net flow, so a battery discharge is not missed.

Commissioning and Acceptance Test Procedure

The acceptance test proves the export limit holds under realistic conditions. Run it before grid energization sign-off. Pass criteria come from the connection offer or grid code, and your own plan should add internal targets.

Pre-Energization Checklist

• All CTs and meters wired with correct phase rotation, verified with a phase rotation meter.
• All inverter communication addresses unique and registered with the controller.
• Setpoint, dead-band, ramp rate and timeout configured per design.
• Communication backbone checked from the controller to every inverter.
• Inverter firmware meets the manufacturer’s minimum for export limit support, per the release notes.

Test 1: Steady-State Limit

Bring the system online in clear daytime conditions. Confirm grid power at the PCC stays at or below the setpoint over a defined period, and record how far power oscillates around the setpoint.

Test 2: Load Step Response

Drop a major on-site load, such as a chiller or process line, and measure the time from load drop to inverter throttle. Compare it with the response requirement.

Test 3: Setpoint Timeout

Disconnect the controller from the inverters. Confirm every inverter reaches its safe state within the configured timeout.

Test 4: Inverter Fault Recovery

Trip one inverter manually. Confirm the remaining inverters do not breach the cap during the trip and the system rebalances.

Test 5: 24-Hour Trend

Leave the system running for 24 hours with full data logging. Review the trend log for spurious export events, oscillation around the setpoint and missed throttle commands.

Document every test result with timestamps and meter values. The network operator may request the trend log as part of the connection sign-off package.

Eight Common Export Limitation Design Mistakes

These mistakes appear again and again when export limit commissioning goes wrong. The descriptions are generic patterns, not reports of specific sites.

Mistake 1: Sizing for Average Load Instead of Load Floor

Designers anchor on average daytime demand. When the load falls on light days, the system curtails heavily. Anchor sizing on a low percentile of daytime load, and use the average only as an upper bound for systems with storage.

Mistake 2: Wrong Side of the Generator Transfer Switch

The CT is placed on the building side of a generator transfer switch instead of the utility side. During testing, the controller reads generator output as load and lets PV inject. Place the CT or meter on the utility-facing side of any source transfer device.

Mistake 3: Mixing Inverter Brands Without Verified Compatibility

A cluster of mixed brands is commissioned with a vendor-agnostic gateway, and one firmware revision does not implement the power limit register as expected. Verify support for the exact model and firmware of every inverter before specifying a vendor-agnostic gateway. When in doubt, use single-vendor clusters.

Mistake 4: Setting the Dead-Band Too Tight

If the operator requires zero export with a small tolerance and the dead-band is set to zero, the loop can oscillate across the tolerance and occasionally export. Set the dead-band to a fraction of the tolerance, and bias the setpoint slightly into import so normal oscillation stays inside the limit.

Mistake 5: Ignoring Ramp Rate

If the inverter ramp rate is left at a slow default, a load drop leads to a slow throttle and power flows to the grid during the ramp. Set the ramp rate to the fastest value the grid code allows, and check flicker compliance separately.

Mistake 6: No Battery Pre-Charge Logic

If the controller only charges the battery from surplus, the battery is empty when the surplus starts and the morning ramp curtails at the inverter. Use pre-charge logic based on the irradiance forecast so charging starts before curtailment triggers.

Mistake 7: Communication Failure Mode Not Checked

If a communication cable is disconnected during maintenance, the inverters wait for the timeout and then trip or curtail, and production stops even though the cause was brief. Test the failure mode at commissioning, set the timeout to the longest value the operator accepts, and add a reconnect retry.

Mistake 8: No Trend Logging

Without logs, a dispute with the network operator has no evidence. Log meter readings, setpoint commands and inverter responses at fine resolution to non-volatile storage, and keep the history for as long as the connection conditions require.

Economic Impact of Export Limitation

Export limitation changes project economics in three ways. This section gives the structure of the calculation, because costs and timelines depend on the site and the operator.

Curtailment Cost

The first-order cost is the lost generation. Annual curtailment loss in kWh times the value of self-consumed energy gives the lost revenue. Use the load-matched model, not a flat percentage.

Avoided Interconnection Upgrade

The first-order benefit is avoiding the network upgrade that would be needed to allow full export. Ask the operator for a quote for both options: a limited connection and a full-export connection with upgrade.

Connection Timeline

A limited connection may be approved faster than an unrestricted one on a constrained feeder. Ask the operator for expected timelines for both options, then value the earlier start in production and cost of capital.

Battery Storage Payback

Battery payback on an export-limited site is the installed battery cost divided by the annual value of recovered energy. Use your own quote, the modeled recovered kWh per year after round-trip losses, and the avoided import price. Compare it with the same battery on a site without a limit, where time-of-use arbitrage is the main benefit.

Software Workflow for Export-Limited Designs

An export-limited project needs load profile import, irradiance simulation, curtailment calculation, battery sizing and a controller architecture in one set of assumptions. SurgePV’s published scope covers 3D roof modeling, array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output and proposal generation. Whether a given tool models an export cap and battery dispatch against your load data is something to check in a demo, using your own interval data.

A workable process for an export-limited project runs in five stages with solar design software or equivalent tools:

1. Project setup. Import the site location, roof geometry and load profile in the format the utility provides, for example 30-minute kWh in CSV.
2. System sizing. Run candidate array sizes against the export cap as a constraint.
3. Curtailment modeling. Simulate hourly generation against the load profile, and record curtailed kWh and the percentage loss for each candidate size.
4. Storage sizing. Add battery options and rerun with charge and discharge logic, to find the size that meets the curtailment tolerance at the lowest cost per recovered kWh.
5. Proposal and documentation. Produce the customer proposal with the curtailment result, payback math and controller architecture diagram, and pass the equipment list to procurement.

Conclusion

• Anchor sizing on the load floor, not the average. The low-percentile daytime load is the practical upper bound of non-curtailed PV without storage.
• Verify compatibility before specifying a multi-vendor cluster. Mixed-brand systems work only when every inverter model and firmware accepts the power limit commands.
• Run the five-test acceptance protocol before grid sign-off. Steady-state, load step, setpoint timeout, inverter fault and 24-hour trend. Having the results in hand shortens every later audit.

To test array and battery sizes against your own load data, book a SurgePV demo.

Frequently Asked Questions

What is export limitation in a commercial solar system?

Export limitation is a control strategy that caps the power a PV system can send to the grid. A meter or current transformer at the point of common coupling measures net flow, and a controller reduces inverter output when export approaches the setpoint. The limit can be a fixed kW cap, a dynamic cap or absolute zero.

How does a zero export solar system work?

A zero export system measures net power flow at the service entrance and throttles the inverters whenever power starts to flow toward the grid. A controller reads the meter or CTs and sends power limit commands to the inverters, usually over Modbus or an analog signal. The loop must respond faster than the grid code or connection offer allows.

What hardware do you need for a zero export commercial PV system?

You need a meter or current transformers at the point of common coupling, a controller or gateway, and inverters that accept external power limit commands. Some inverters run the control loop in firmware with a CT input, so a separate gateway may not be needed. Multi-inverter sites also need a communication backbone such as Modbus RTU or TCP.

How much energy do you lose to a zero export limit?

The loss depends on how the array size compares with the site’s daytime load, including weekends. A site that always uses more than the array produces loses little, while a weekend-idle site loses a large share. In this guide’s one-day illustration, a 500 kW array lost about 20% on a weekday and about 78% on a weekend.

Can you do zero export with multiple inverters?

Yes. The controller reads total grid power at the point of common coupling and divides the limit command across the inverters in the cluster. Check that every inverter model and firmware version accepts external power limit commands, and test mixed-brand clusters at commissioning.

Is export limitation the same as anti-islanding?

No. Anti-islanding disconnects the inverter when the grid is lost, while export limitation throttles output when the grid is energized. Both can apply to the same site, and each is set by the interconnection standard and connection offer that govern it.

Does zero export design change the optimal system size?

Yes. Without export, the target shifts from maximum annual kWh to maximum useful kWh. Size the array to the daytime load floor for low curtailment, or oversize it and add storage to absorb the surplus, and test the result against weekday and weekend load.